docs/releases/1.15-NOTES.md
The kops apiGroup is changing from kops to kops.k8s.io, which means that
downgrading to kops 1.14 after upgrading to kops 1.15 will not recognize the
newer objects. (In general it's better not to mix kops versions, but it is more
visible here.) Please back up your manifest files using kops get <clustername> -oyaml before upgrading, if the need arises these can later be restored with
kops 1.14 with kops replace -f.
It should also be possibe to rewrite the apiGroup fom kops to kops.k8s.io on
a yaml backup using sed or a similar tool, but taking a precautionary backup
is safer.
kops to kops.k8s.io, to
support CRDs. You can continue to provide either apiGroup as input (but you
should ideally move to kops.k8s.io), but the output will always be of the
kops.k8s.io form.--cloudonly case is much faster than previously, which we believe to be
correct because we expect this is normally for disaster-recovery scenarios,
but you may want to specify longer timings via flags if you are relying on
time-based delays.If checking the output as a string (yaml or json), please note that the apiGroup will now be kops.k8s.io, not kops. If performing strict string comparison you will need to update your expected values.
Kubernetes 1.9 users will need to enable the PodPriority feature gate. This is required for newer versions of kOps.
To enable the Pod priority feature, follow these steps:
kops edit cluster
# Add the following section
spec:
kubelet:
featureGates:
PodPriority: "true"
$ @xichengliudui #6802go test command @justinsb #7003