-
Notifications
You must be signed in to change notification settings - Fork 591
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
Run upgrade tests #1656
Comments
We do basic upgrade tests from v1 to v2 in the https:/kong/charts repository on each PR right now, just a heads up. |
I ran through https://gist.github.com/rainest/cf4db9b0e607f0e719470166f3cf2634 (install all the 1.3 flat manifests, confirm some basic Ingress handling, install the equivalent 2.0.0-alpha.3 manifest over top, confirm updated Pods come online and that the Ingress still routes) successfully earlier. The caveats then were:
All but the third of those has been addressed in the beta, and the third we can't really address beyond documentation (you just have to manually delete the old SA and binding). Is there anything further we wanted to test? |
Image kong/kubernetes-ingress-controller:2.0.0-beta.2 should have resolved issue 1 &2. Interms of of 3, I would propose a prepare/cleanup function within 2.x controller, which basically remove all non-used (1.x) RBAC role names and bindings before KIC ready for work. Or put it another word, only keep 2.x required RBAC role in the cluster. actionable item |
Kong/charts#450 is a known upgrade regression in KIC 2.0. |
Is there an existing issue for this?
Problem Statement
We have breaking changes in 2.0, user would have broken controller after upgrade.
Proposed Solution
We need ensure there is no regression when user upgrade from 1.3 to 2.0
Run upgrade tests against beta
Run upgrade tests against Kong Enterprise
Additional information
No response
Acceptance Criteria
No response
The text was updated successfully, but these errors were encountered: