-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Add Kubernetes 1.6 support to Juju charms #44500
Add Kubernetes 1.6 support to Juju charms #44500
Conversation
Hi @Cynerva. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@k8s-bot ok to test |
/approve |
/assign @marcoceppi |
@k8s-bot verify test this |
master: Fix start_master args
Credit to @tvansteenburgh, thanks!
Pushed updates to hacks/verify-flags/exceptions.txt to cover the new stuff in kubernetes_worker.py. |
/approve |
/lgtm |
@smarterclayton @liggitt Could either of you two take a quick look at this PR? It seems that the k8s bot didn't tag anyone from the owners file of the HACK dir which is holding things up here as we're pending a /approve /lgtm. |
@k8s-bot non-cri e2e test this |
/approve verify-flags changes |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cynerva, liggitt, marcoceppi
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 43000, 44500, 44457, 44553, 44267) |
What this PR does / why we need it:
This adds Kubernetes 1.6 support to Juju charms.
This includes some large architectural changes in order to support multiple versions of Kubernetes with a single release of the charms. There are a few bug fixes in here as well, for issues that we discovered during testing.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Thanks to @marcoceppi, @ktsakalozos, @jacekn, @mbruzek, @tvansteenburgh for their work in this feature branch as well!
Release note: