Closed youreddy closed 5 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/161770610
The labels on this github issue will be updated when the story is started.
Hey youreddy!
Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.
What this PR does / why we need it:
This PR bumps the kubernetes binaries to v1.12.2. Additionally, it includes changes to generate a serving certificate for kube-controller-manager. v1.12.2 now requires either to have a self-signed certificate created to a specified
--cert-dir
or supply the proper certificate and private key via--tls-cert-file
and--tls-private-key-file
.How can this PR be verified? Deploy a CFCR cluster with these changes. Run integration, conformance, and upgrade against it.
Is there any change in kubo-release? Yes: https://github.com/cloudfoundry-incubator/kubo-release/pull/271
Is there any change in kubo-ci? Nope.
Does this affect upgrade, or is there any migration required? Yes, because its an update of the k8s binaries.
Which issue(s) this PR fixes: None.
Release note: