Sitelet https://github.com/kubernetes/kops/pull/18599/files
Skip to content

docs: update 1.36 release notes post-release #18599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kubernetes-prow merged 1 commit into from
Jul 16, 2026
Merged

docs: update 1.36 release notes post-release #18599

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions docs/releases/1.36-NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,5 @@
## Release notes for kOps 1.36 series

**⚠ kOps 1.36 has not been released yet! ⚠**

This is a document to gather the release notes prior to the release.

kOps 1.36 adds Kubernetes 1.36 support, completes the move away from the in-tree cloud providers, refreshes the bundled components (containerd v2.2, etcd-manager, AWS Load Balancer Controller, EBS CSI driver, Cilium options, CoreDNS, etc.), reworks how the `kops-channels` addon manager is built and deployed, refreshes Karpenter support with kOps-managed `EC2NodeClass` and `NodePool` objects, introduces a hybrid bootstrap path for gossip clusters, expands Azure and Hetzner support, and lays the groundwork for Linode (Akamai) as a new cloud provider.

# Significant changes
Expand Down Expand Up @@ -261,6 +257,6 @@ This feature is currently supported on Debian-family distributions only (Debian,

* The standalone `channels` binary is no longer distributed in kOps 1.36; `kops-channels` runs as a static pod on the control plane.

* Support for AWS Classic Load Balancer (CLB) for the API, deprecated since kOps 1.26, will be rejected for new clusters in kOps 1.37 and fully removed (existing clusters must migrate) in kOps 1.38. See the [CLB to NLB migration guide](https://github.com/kubernetes/kops/blob/master/permalinks/acm_nlb.md) for the upgrade procedure.
* Support for AWS Classic Load Balancer (CLB) for the API, deprecated since kOps 1.26, will be removed in kOps 1.37. New clusters using CLB will be rejected, and existing clusters will need to migrate to NLB before they can be upgraded. See the [CLB to NLB migration guide](https://github.com/kubernetes/kops/blob/master/permalinks/acm_nlb.md) for the procedure.

* Support for gossip DNS is deprecated. kOps 1.37 will reject new gossip DNS clusters, and kOps 1.38 will require existing gossip DNS clusters to migrate before upgrading. This affects clusters whose name ends in `.k8s.local` and that were not created with `--dns=none`; clusters using `--dns=none`, even with a `.k8s.local` name, are not affected. Existing gossip DNS clusters should migrate to `--dns=none` or a hosted DNS zone. kOps 1.36 introduces hybrid bootstrap to make that migration easier.
* Support for gossip DNS, deprecated since kOps 1.29, will be removed in kOps 1.37. New gossip clusters will be rejected, and existing clusters will need to migrate before they can be upgraded. This affects clusters whose name ends in `.k8s.local` and that were not created with `--dns=none`; clusters using `--dns=none`, even with a `.k8s.local` name, are not affected. Migrate to `--dns=none` or a hosted DNS zone; kOps 1.36 introduces hybrid bootstrap to make that migration easier.
Loading