Skip to content

Releases: kubernetes/kops

v1.29.0-beta.1

15 Mar 20:46
f0537f4
Compare
Choose a tag to compare
v1.29.0-beta.1 Pre-release
Pre-release

This is the first beta of the 1.29 release.

Significant changes

Deferred deletion / pruning phase

Some infrastructure changes are potentially disruptive to the continued
operation of the cluster. For the most disruptive operations, particularly
those that break rolling-update of the cluster, we have started to use deferred
deletion to minimize the impact. For example, on AWS we create a second NLB
during the kops update phase when we cannot change the NLB directly.
kops update will report that a --prune is needed. To minimize disruption,
we recommend you perform this after a rolling-update, for example:

kops update $MYCLUSTER --yes --admin
kops rolling-update $MYCLUSTER --yes
kops update $MYCLUSTER --yes --admin --prune # NEW!

Deferred deletion is currently used to safely introduce security groups for NLBs on AWS,
and to move to an internal load balancer for kops-controller on GCP.

Initial OpenTelemetry Support

We are starting to add (experimental) support for OpenTelemetry,
in particular Tracing support. Setting OTEL_EXPORTER_OTLP_TRACES_FILE
will write a trace file which can then be read by the traceserver program.
More information and options are described in docs/opentelemetry.md.
The tracing data is not expected to be particularly useful for end-users in
this release; the (non-standard) recording approach is instead intended to
work well with our Prow end-to-end testing system so that developers can
optimize kOps.

Please note: this is not telemetry in the "phone-home" sense.
The kOps project does not collect data from your machine. As an
open-source project we do not even want to collect any of your data.
Currently the only OpenTelemetry backend supported is writing to a
filesystem (and it is opt-in). In future you will be able to configure
other OpenTelemetry backends, but this data will only be sent if
you enable OpenTelemetry, and only sent to where you configure.

AWS

  • Network Load Balancers in front of the Kubernetes API and bastion hosts now
    have a security group attached. These security groups are used for security group rules
    allowing incoming traffic to the NLBs as well as traffic between the NLBs and their target
    instances.

  • Posts event data to URL upon instance interruption action in aws-node-termination-handler with WEBHOOK_URL.

GCP

  • As of Kubernetes version 1.29, credentials for private GCR/AR repositories will be handled by the out-of-tree credential provider. This is an additional binary that each instance downloads from the assets repository.

  • We now use a private load-balancer for in-cluster traffic on GCP, which allows us
    to use network tags to restrict access only to the cluster nodes.

Breaking changes

  • kops toolbox dump limits the number of nodes dumped to 500 by default. Use --max-nodes to override.

  • Support for Kubernetes version 1.23 has been removed.

Known Issues

Deprecations

  • Support for Kubernetes version 1.24 is deprecated and will be removed in kOps 1.30.

  • Support for Kubernetes version 1.25 is deprecated and will be removed in kOps 1.31.

  • Support for AWS Classic Load Balancer for API is deprecated and should not be used for newly created clusters.

  • All legacy addons are deprecated in favor of managed addons, including the metrics server addon and the autoscaler addon.

What's Changed

v1.28.4

02 Feb 15:49
3d5c6ce
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.28.3...v1.28.4

v1.27.3

02 Feb 14:33
6552c30
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.27.2...v1.27.3

v1.28.3

26 Jan 15:49
79813ba
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.28.2...v1.28.3

v1.29.0-alpha.3

22 Dec 14:40
0300a3b
Compare
Choose a tag to compare
v1.29.0-alpha.3 Pre-release
Pre-release

Release v1.29.0-alpha.3

What's Changed

New Contributors

Full Changelog: v1.29.0-alpha.2...v1.29.0-alpha.3

v1.28.2

22 Dec 15:03
6c7cdf2
Compare
Choose a tag to compare

Release v1.28.2

What's Changed

Full Changelog: v1.28.1...v1.28.2

v1.29.0-alpha.2

13 Nov 08:25
8916d1e
Compare
Choose a tag to compare
v1.29.0-alpha.2 Pre-release
Pre-release

What's Changed

v1.28.1

13 Nov 09:59
2038e4c
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.28.0...v1.28.1

v1.27.2

13 Nov 09:58
e2d811c
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.27.1...v1.27.2

v1.28.0

23 Sep 16:18
c07f51e
Compare
Choose a tag to compare

Release notes for kOps 1.28 series

Significant changes

AWS

  • Node Termination Handler is now enabled by default.

GCP

  • metadata-proxy is no longer deployed on GCP clusters for Kubernetes 1.29+.

Breaking changes

AWS

  • The kops get assets --copy command no longer sets object-level public-read ACLs in the destination fileRepository.
    h

Other breaking changes

  • Support for Kubernetes version 1.22 has been removed.

  • Support for Ubuntu 18.04 is has been removed.

  • Support for Canal, Flannel, and Kube-Router has been removed for Kubernetes 1.28 and later.

  • RHEL-based distros will no longer have wget, curl, python2, and git packages installed. Install them with hooks if needed.

Deprecations

  • Support for Kubernetes version 1.23 is deprecated and will be removed in kOps 1.29.

  • Support for Kubernetes version 1.24 is deprecated and will be removed in kOps 1.30.

  • Support for AWS Classic Load Balancer for API is deprecated and should not be used for newly created clusters.

  • All legacy addons are deprecated in favor of managed addons, including the metrics server addon and the autoscaler addon.

What's Changed