-
Notifications
You must be signed in to change notification settings - Fork 268
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
Old versions of k8s remove from testing #511
Conversation
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
@bwagner5 I'm thinking this change should go into a 1.14 release of NTH rather than 1.13.4, since removing support for k8s < 1.14 could be a breaking change for some customers. Should we do a release of 1.13.4 first and then merge this afterward (and maybe also #506, since it's also a large change)? |
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.
Thank you for taking care of all this! Once the tests pass and we decide on the release strategy, I'll approve and merge.
Ran the end-to-end tests on my local machine and they all passed. Not sure why they keep failing in GitHub Actions, but I'm comfortable with merging this once we're ready. |
@snay2 Yep, that sounds good on putting this v1.14.0 |
Also allow more verbose kind output to ease debugging
Upgrade k8s image to 1.22.2 to avoid kind errors
Bother. I'm getting the same error locally now that the build here is getting:
Looks like 1.22 drops the "apiextensions.k8s.io/v1beta1" in favor of "apiextensions.k8s.io/v1": https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/ |
Just seen that.. Will fix it and update tomorrow morning |
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
@snay2 i have fixed it at known places. please check. |
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
@snay2 can we use latest version of helm chart for |
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
Signed-off-by: Nitin Goyal <nitingoyal.dev@gmail.com>
@snay2 all test are passed with new prometheus operator. |
@snay2 can you rerun failed step as it passed in my gut workflow. Not sure why failed |
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.
Nice work, thanks for seeing this through.
Issue #, if available: #507
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.