-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hawkbit: Use networking.k8s.io/v1 for Ingress if available #314
Conversation
@laverman @kaizimmerm could any of you take a look at this |
helm-chart is not supported anymore? |
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: |
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. @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. |
Apply change from PR #314: Hawkbit: Use networking.k8s.io/v1 for Ingress if available
Commit merged via #550, available in chart version 1.6.1. |
This PR adds support for the v1 Ingress resource which is necessary for a deployment to Kubernetes 1.22.