Add release notes for deleting the kops-controller deployment

This commit is contained in:
Peter Rifel 2020-01-12 07:38:22 -06:00
parent 179957d09f
commit 9389700b94
4 changed files with 29 additions and 3 deletions

View File

@ -1,6 +1,6 @@
# Architecture: kops-controller
kops-controller runs as a container on the master node(s). It is a kubebuilder
kops-controller runs as a DaemonSet on the master node(s). It is a kubebuilder
controller, that performs runtime reconciliation for kops.
Controllers in kops-controller:

View File

@ -23,7 +23,9 @@ the notes prior to the release).
# Required Actions
* No required actions yet known.
* If either a Kops 1.16 alpha release or a custom Kops build was used on a cluster,
a kops-controller Deployment may have been created that should get deleted.
Run `kubectl -n kube-system delete deployment kops-controller` after upgrading to Kops 1.16.0-beta.1 or later.
# Full change list since 1.15.0 release

View File

@ -19,7 +19,9 @@ the notes prior to the release).
# Required Actions
* No required actions yet known.
* If either a Kops 1.17 alpha release or a custom Kops build was used on a cluster,
a kops-controller Deployment may have been created that should get deleted because it has been replaced with a DaemonSet.
Run `kubectl -n kube-system delete deployment kops-controller` after upgrading to Kops 1.17.0-alpha.2 or later.
# Full change list since 1.16.0 release

View File

@ -0,0 +1,22 @@
## Release notes for kops 1.18 series
(The kops 1.18 release has not been released yet, this is a document to gather
the notes prior to the release).
# Breaking changes
* Please see the notes in the 1.15 release about the apiGroup changing from kops
to kops.k8s.io
* Since 1.16, a controller is now used to apply labels to nodes. If
you are not using AWS, GCE or OpenStack your (non-master) nodes may
not have labels applied correctly.
# Significant changes
# Required Actions
* If a custom Kops build was used on a cluster, a kops-controller Deployment may have been created that should get deleted.
Run `kubectl -n kube-system delete deployment kops-controller` after upgrading to Kops 1.16.0-beta.1 or later.
# Full change list since 1.16.0 release