-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
Migrates addons from RCs to Deployments #36008
Conversation
32d51d3
to
745d306
Compare
Jenkins GCE Node e2e failed for commit 745d306. Full PR test history. The magic incantation to run this job again is |
kubernetes.io/cluster-service: "true" | ||
spec: | ||
replicas: __PILLAR__DNS__REPLICAS__ |
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.
Where does the initial replica count live now?
Maybe leave a comment here specifically saying # replicas: not specified here, see xyz.yaml
or maybe even specify why.
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.
Same for other DNS files :)
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.
They live nowhere for now. I want to hand over this responsibility to the DNS horizontal autoscaler.
As for this RC -> Deployment migration, kube-dns might rely on the dns autoscaler in order to be re-scaled to a proper number, otherwise the new kube-dns Deployment would have 1 replica by default. For the future upgrades(Deployment -> Deployment), the replica count would not got clobbered anymore.
spec: | ||
hostNetwork: true | ||
containers: | ||
- name: kube-addon-manager | ||
# When updating version also bump it in cluster/images/hyperkube/static-pods/addon-manager.json | ||
image: gcr.io/google-containers/kube-addon-manager:v5.2 | ||
image: gcr.io/zihongz-k8s-dev/kube-addon-manager:v6.0 |
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.
don';t forget to change this back!
745d306
to
34d713c
Compare
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.
LGTM Dashboard UI changes
34d713c
to
1b6e6bd
Compare
Jenkins Kubemark GCE e2e failed for commit 1b6e6bd9a081e7793004cc1e8ee7a0b313d180e3. Full PR test history. The magic incantation to run this job again is |
1b6e6bd
to
731082e
Compare
Thanks @bryk for reviewing. Bumped up Addon Manager to v6.0-alpha.1 and removed WIP. Will send another PR to bump up Addon Manager to v6.0 after kubernetes v1.5.0.beta is cut. It would be great if this could got LGTM earlier in order to test the new Addon Manager and addons over this weekend. @mikedanese @piosz @bprashanth |
Release-czar approved post-code freeze merge--This was LGTMed and in the merge-queue at code freeze time for 1.5. Leaving 1.5 milestone to let it gets merged after code freeze. |
6a9a4cd
to
fe3a0d2
Compare
Jenkins GKE smoke e2e failed for commit fe3a0d2. Full PR test history. The magic incantation to run this job again is |
Jenkins unit/integration failed for commit fe3a0d2. Full PR test history. The magic incantation to run this job again is |
Rebased and passed tests. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Fixes #33698.
Below addons are being migrated:
For the new deployments, the version suffixes are removed from their names. Version related labels are also removed because they are confusing and not needed any more with regard to how Deployment and the new Addon Manager works.
The
replica
field inkube-dns
Deployment manifest is removed for the incoming DNS horizontal autoscaling feature #33239.The
replica
field inDashboard
Deployment manifest is also removed because the rescheduler e2e test is manually scaling it.Some resource limit related fields in
heapster-controller.yaml
are removed, as they will be set up by theaddon resizer
containers. Detailed reasons in #34513.Three e2e tests are modified:
rescheduler.go
: Changed to resize Dashboard UI Deployment instead of ReplicationController.addon_update.go
: Some namespace related changes in order to make it compatible with the new Addon Manager.dns_autoscaling.go
: Changed to examine kube-dns Deployment instead of ReplicationController.Both of above two tests passed on my own cluster. The upgrade process --- from old Addons with RCs to new Addons with Deployments --- was also tested and worked as expected.
The last commit upgrades Addon Manager to v6.0. It is still a work in process and currently waiting for #35220 to be finished. (The Addon Manager image in used comes from a non-official registry but it mostly works except some corner cases.)
@piosz @gmarek could you please review the heapster part and the rescheduler test?
@mikedanese @thockin
cc @kubernetes/sig-cluster-lifecycle
Notes:
-v1.2.0
suffix) for avoiding describe this upgrade transition explicitly. In this way we don't need to attach fake apply labels to the old Deployments.This change is