-
Notifications
You must be signed in to change notification settings - Fork 23
Document Helm 4 support #1150
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.
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
base: main
Are you sure you want to change the base?
Document Helm 4 support #1150
Conversation
✅ Deploy Preview for okteto-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| - **Build Queue System**: Okteto now implements a build queue system that ensures consistent build performance and fair resource distribution. Build requests are automatically routed to the optimal Okteto Build pod based on real-time metrics (CPU pressure, memory usage, and IOPS). When all build pods are busy, builds enter a queue and wait until resources become available, preventing overload and ensuring predictable build times. This behavior is enabled by default but can be disabled by setting the `OKTETO_BUILD_QUEUE_ENABLED` feature flag to `false` via [Admin Variables](admin/dashboard.mdx#admin-variables). Learn more about the [Build Queue System](core/build-service.mdx#build-queue-system) | ||
|
|
||
| - **Helm 4 Support (Opt-in)**: Helm 4 is now available alongside Helm 3 for testing and validation. Helm 3 remains the default in this release. Helm 4 introduces server-side apply (SSA) as the default behavior, which changes how Kubernetes resources are created and tracked. Most charts will work without modifications. Test your deployments with Helm 4 before it becomes the default in Okteto 1.42. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test your deployments with Helm 4 before it becomes the default in Okteto 1.42.
This part feels a bit too urgent. Could we say Test your deployments with Helm 4 in Okteto. We'll make Helm 4 the default in 1.42, with the option to stay on Helm 3 if needed.
|
|
||
| - **Helm 4 Support (Opt-in)**: Helm 4 is now available alongside Helm 3 for testing and validation. Helm 3 remains the default in this release. Helm 4 introduces server-side apply (SSA) as the default behavior, which changes how Kubernetes resources are created and tracked. Most charts will work without modifications. Test your deployments with Helm 4 before it becomes the default in Okteto 1.42. | ||
|
|
||
| **How to test Helm 4:** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think the options below this are too much info for the release notes? Not sure if we should defer this to https://www.okteto.com/docs/self-hosted/manage/upgrade/ page
| ``` | ||
| - To revert, change `helm4` back to `helm` or use the `helm3` command explicitly | ||
|
|
||
| **Important**: Helm 4 will become the default Helm binary in **Okteto 1.42**. We recommend testing your deployments with Helm 4 now to ensure a smooth transition. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| **Important**: Helm 4 will become the default Helm binary in **Okteto 1.42**. We recommend testing your deployments with Helm 4 now to ensure a smooth transition. | |
| **Important**: Helm 4 will become the default in Okteto 1.42, with the option to continue using Helm 3. We recommend testing your deployments with Helm 4 ahead of time. |
No description provided.