-
Notifications
You must be signed in to change notification settings - Fork 289
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
Kubernetes: Ingress extensions/v1beta1 -> networking.k8s.io/v1beta1 #368
Kubernetes: Ingress extensions/v1beta1 -> networking.k8s.io/v1beta1 #368
Conversation
Looks good. |
Will do that later this day, if no one is faster 😎 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Hey @SoftCreatR did you try updating by installing the old chart (let's say from current develop), then running helm upgrade with your changes applied? |
Didn't had the time, yet. |
@SoftCreatR Any update on this PR, yet? |
Sorry for the late reply. There you go: helm install -dry-run --verbose --version v0.11.0 botkube --create-namespace --namespace="botkube" \
--set communications.slack.enabled=true \
--set communications.slack.channel=botkube-test \
--set communications.slack.token=xoxb-0000000000000-0000000000000-XXXXXXXXXXXXXXXXXXXXXXXX \
--set config.settings.kubectl.enabled=true \
--set image.repository=infracloudio/botkube \
--set image.tag=v0.11.0 \
infracloudio/botkube =>
=> |
Thanks @SoftCreatR,
|
@PrasadG193 I do currently not have an environment to test it with ingress. |
@SoftCreatR It's fine! You don't need that for --dry-run. Adding |
I know, but I currently don't have any Cluster available with ingress set up ;) |
It should work! Can you try |
ISSUE TYPE
SUMMARY
Resource Ingress is deprecated in Kubernetes API
extensions/v1beta1
https://github.com/infracloudio/botkube/blob/c6db9526a3232b210fd05202d104ca18eb3a03c2/helm/botkube/templates/ingress.yaml#L2-L3
Referencing PR: kubernetes/kubernetes#74057
POSSIBLE FIX