Hawkbit: Use networking.k8s.io/v1 for Ingress if available
This PR adds support for the v1 Ingress resource which is necessary for a deployment to Kubernetes 1.22.
@laverman @kaizimmerm could any of you take a look at this
helm-chart is not supported anymore?
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122
I'm also waiting for this. Please merge this PR to keep supporting the helm-chart.
I'm also waiting for this. Please merge this PR to keep supporting the helm-chart.
I give up and maintain it by myself.
By the way, you can add storage class under this line: storageClassName: {{ .Values.fileStorage.storageClass }} (Be careful to indent)
Is this maintained? @bulmust do you have your own version public? Need to add custom serviceAccounts
Is this maintained? @bulmust do you have your own version public? Need to add custom serviceAccounts
I do not publish my own helm chart to anywhere. By the way, this helm chart has a lot of problems like absence of serviceAccounts, storageClass etc, so as I understand this repo does not maintained anymore. You should also consider hawkbit microservice mode which is not compatible with this helm chart.
Alright, thanks for the response! @bulmust, will just copy it and create our own version
Sorry this didn't get attention for so long. @strailov @avgustinmm Any comments on this? It looks good to me. I guess it could make sense to merge this before the hawkbit 0.5.0 update PR.
@PSanetra In order to be able to merge this, the chart (patch) version needs to be updated in the Chart.yaml. This requires a prior git rebase, so that the change is based on the current chart version. Could you do that still? Or, if you don't mind, I could make that change and push to your PR branch (if that was enabled on PR creation).
Commit merged via #550, available in chart version 1.6.1.