Skip to content

Releases: kubernetes/kops

v1.31.0-alpha.1

15 Oct 18:07
@rifelpet rifelpet
v1.31.0-alpha.1
aaa35cc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.31.0-alpha.1 Pre-release
Pre-release

What's Changed

Read more

Contributors

dims, justinsb, and 21 other contributors
Assets 24
Loading

v1.30.1

13 Sep 19:09
@hakman hakman
v1.30.1
b3722a8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.30.1 Latest
Latest

What's Changed

Full Changelog: v1.30.0...v1.30.1

Contributors

rifelpet, hakman, and eliasscosta
Assets 24

v1.30.0

16 Aug 19:19
@justinsb justinsb
v1.30.0
93f6b2c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.30.0

Significant changes

Version updates

kOps 1.30 adds support for kubernetes 1.30, and updates of most of the built-in components.

This release also updates to the next generation AWS SDK (aws-sdk-go-v2), though we do not expect
user-visible changes from this update.

Improved support for Azure

kOps on Azure has been significantly improved in this release.

Embedded asset hashes

Hashes for many kubernetes assets have been embedded into the kOps binary. When using
a well-known asset, we no longer need to download the hash from a well-known location,
which slightly speeds up kOps cluster creation, and also creates a stronger chain-of-trust.

Breaking changes

None known.

Known Issues

None known.

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.

Full changelist

Read more

Contributors

justinsb, multi-io, and 22 other contributors
Assets 24
Loading

v1.29.2

24 Jul 11:26
@justinsb justinsb
v1.29.2
f784ce5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.29.2

(Note that v1.29.1 was not released, due to an problem in the release process)

What's Changed (since v1.29.0)

Full Changelog: v1.29.0...v1.29.2

Contributors

justinsb, rifelpet, and 3 other contributors
Assets 24
Loading

v1.28.7

21 Jul 13:44
@justinsb justinsb
v1.28.7
67ee18a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.28.7

(Note that v1.28.6 was not released, due to a problem in the release process)

What's Changed (since v1.28.5)

Full Changelog: v1.28.5...v1.28.7

Contributors

justinsb, rifelpet, and chubchubsancho
Assets 24
Loading

v1.30.0-beta.1

28 Jun 10:56
@justinsb justinsb
v1.30.0-beta.1
b9c632d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.30.0-beta.1 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v1.30.0-alpha.1...v1.30.0-beta.1

Contributors

justinsb, rifelpet, and 8 other contributors
Assets 24
Loading

v1.30.0-alpha.1

17 May 10:02
@hakman hakman
v1.30.0-alpha.1
86f5d45
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.30.0-alpha.1 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: https://g...

Read more

Contributors

justinsb, multi-io, and 17 other contributors
Assets 24
Loading

v1.29.0

16 May 10:44
@justinsb justinsb
v1.29.0
6d2a691
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.29.0

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.

  • Two additional StorageClasses are created on GCP clusters. These are called balanced-csi and ssd-csi and utilize the GCP Balanced and SSD Persistent Disk volume types respectively.

  • Breaking Change - the default StorageClass has been changed from standard-csi to balanced-csi.

  • 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

Other 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 unmanaged addons (in addons/) are deprecated in favor of managed addons, including the metrics server addon and the autoscaler addon.

What's Changed

Read more

Contributors

dims, justinsb, and 36 other contributors
Assets 24
Loading

v1.28.5

11 May 20:50
@justinsb justinsb
v1.28.5
372e15d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.28.5

What's Changed

Full Changelog: v1.28.4...v1.28.5

Contributors

idealhack and hakman
Assets 24
Loading

v1.29.0-beta.1

15 Mar 20:46
@justinsb justinsb
v1.29.0-beta.1
f0537f4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
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

Read more

Contributors

dims, justinsb, and 23 other contributors
Assets 24
Loading