Add blogpost in sync with the v1.34 Kubernetes release #462
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: manuelbuil <[email protected]>
dereknola
requested changes
Aug 13, 2025
| ## Bug Fixes and Other Notable Changes 🛠️ | ||
| We've also been busy tackling a number of bugs, tech debt items and making other important improvements under the hood: | ||
|
|
||
| Numerous bug fixes, including those for secrets encryption rotation timeouts, DNS fallbacks, secrets encryption race conditions, various authorization and authentication handling issues or replacing go-bindata with the go native embed package. |
There was a problem hiding this comment.
Suggested change
| Numerous bug fixes, including those for secrets encryption rotation timeouts, DNS fallbacks, secrets encryption race conditions, various authorization and authentication handling issues or replacing go-bindata with the go native embed package. | |
| Numerous bug fixes, including those for secrets encryption timeouts and race conditions, DNS fallbacks, various authentication handling issues and replacing go-bindata with the go native embed package. |
| We are now generating and managing certificates for kube-scheduler and kube-controller-manager, and they can be rotated using our existing certificate rotation [tool](https://docs.k3s.io/cli/certificate). | ||
|
|
||
| #### Retention Flag for S3 Stored Snapshots 💾 | ||
| We've added a new retention flag for snapshots stored in an S3 bucket. This allows you to keep snapshots in S3 for longer periods while maintaining a smaller number of local snapshots, helping to reduce the required storage for snapshots. This is a great feature for balancing long-term disaster recovery with local storage efficiency. Check out our [docs](https://docs.k3s.io/cli/etcd-snapshot#s3-retention) for more information about how to use it. |
There was a problem hiding this comment.
Suggested change
| We've added a new retention flag for snapshots stored in an S3 bucket. This allows you to keep snapshots in S3 for longer periods while maintaining a smaller number of local snapshots, helping to reduce the required storage for snapshots. This is a great feature for balancing long-term disaster recovery with local storage efficiency. Check out our [docs](https://docs.k3s.io/cli/etcd-snapshot#s3-retention) for more information about how to use it. | |
| We've added a new retention flag for snapshots stored in an S3 bucket. This allows you to keep snapshots in S3 for longer periods while maintaining a smaller number of local snapshots. This is a great feature for balancing long-term disaster recovery with local storage efficiency. Check out our [docs](https://docs.k3s.io/cli/etcd-snapshot#s3-retention) for more information about how to use it. |
| Here’s a look at some of the most impactful features and updates we've rolled out: | ||
|
|
||
| #### Automatic Certificate Renewal Window Increase 📅 | ||
| We've made certificate management more user-friendly. We increased the automatic certificate renewal window from 90 to 120 days. This means if you perform quarterly upgrades, your certificates will be renewed more frequently, preventing them from expiring and making your clusters unusable. For more information check our [docs](https://docs.k3s.io/cli/certificate#client-and-server-certificates) |
There was a problem hiding this comment.
Suggested change
| We've made certificate management more user-friendly. We increased the automatic certificate renewal window from 90 to 120 days. This means if you perform quarterly upgrades, your certificates will be renewed more frequently, preventing them from expiring and making your clusters unusable. For more information check our [docs](https://docs.k3s.io/cli/certificate#client-and-server-certificates) | |
| We've made certificate management more user-friendly by increasing the automatic certificate renewal window from 90 to 120 days. This means if you perform quarterly upgrades, your certificates will be renewed more frequently, preventing them from expiring and making your clusters unusable. For more information check our [docs](https://docs.k3s.io/cli/certificate#client-and-server-certificates) |
| We've made certificate management more user-friendly. We increased the automatic certificate renewal window from 90 to 120 days. This means if you perform quarterly upgrades, your certificates will be renewed more frequently, preventing them from expiring and making your clusters unusable. For more information check our [docs](https://docs.k3s.io/cli/certificate#client-and-server-certificates) | ||
|
|
||
| #### Optional Airgap Image Tarball Imports 💨 | ||
| For those who use K3s in an airgap environment, you now have the option to skip importing all image tarballs. You could select to import only images that have changed since they were last imported, even across restarts. This can significantly speed up the startup process, as the kubelet can start sooner. Check our [docs](https://docs.k3s.io/installation/airgap?airgap-load-images=Manually+Deploy+Images#enable-conditional-image-imports) for more information |
There was a problem hiding this comment.
Suggested change
| For those who use K3s in an airgap environment, you now have the option to skip importing all image tarballs. You could select to import only images that have changed since they were last imported, even across restarts. This can significantly speed up the startup process, as the kubelet can start sooner. Check our [docs](https://docs.k3s.io/installation/airgap?airgap-load-images=Manually+Deploy+Images#enable-conditional-image-imports) for more information | |
| For those who use K3s in an airgap environment, you now have the option to skip importing all image tarballs. You can select to import only images that have changed since they were last imported, even across restarts. This can significantly speed up the startup process when deploying a large number of images, as the kubelet can start sooner. Check our [docs](https://docs.k3s.io/installation/airgap?airgap-load-images=Manually+Deploy+Images#enable-conditional-image-imports) for more information |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft to prepare a blog post with our release