Conversation
codyjlandstrom
requested review from
ifbyol,
pchico83 and
rlamana
as code owners
✅ Deploy Preview for okteto-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| ### Bug Fixes {#bug-fixes-1.42} | ||
|
|
||
| - |
There was a problem hiding this comment.
@ifbyol I don't believe there's anything to call out here?
There was a problem hiding this comment.
There is a small fix in the chart. We fixed a panic in the API that happened in very rare situations where a kubernetes resource was restarting and an error message wasn't being indicated by Kubernetes. That was provoking a restart in the API container
| ### Improvements {#improvements-1.42} | ||
|
|
||
| - **Persistent Namespace and Preview Indicators**: Namespaces and Preview Environments marked as [persistent](core/namespaces.mdx#mark-a-namespace-as-persistent-to-prevent-it-from-sleeping-and-deletion) now display a visual indicator in both the Okteto Dashboard and the CLI (`okteto namespace list` and `okteto preview list`), making it easier to identify which environments are exempt from automatic sleep and garbage collection <!-- 9986 --> | ||
| - Updated the Deploy dialog UI with a new drawer design for improved consistency across the Dashboard <!-- DEV-1263 --> |
There was a problem hiding this comment.
Considering adding a screenshot for these
There was a problem hiding this comment.
Yeah, I think it might be a good idea. We might to revisit also the docs, as we have some screenshot of the deploy dialog like: https://www.okteto.com/docs/admin/private-repositories/ssh-key/#deploy-a-private-repository
| ### New Features {#new-features-1.42} | ||
|
|
||
| - **Build Queue Enabled by Default**: The [build queue system](core/build-service.mdx#build-queue-system) introduced as opt-in in 1.41 is now enabled by default. Build requests are automatically routed to the optimal Okteto Build pod based on real-time metrics, and when all build pods are busy, builds enter a queue to ensure consistent performance. Customers on significantly older CLI versions will continue using the legacy build path automatically. If you need to opt out, set the admin variable `OKTETO_BUILD_QUEUE_ENABLED` to `false` via [Admin Variables](admin/dashboard.mdx#admin-variables) | ||
| - **Gateway API Support (Preview)**: Added initial support for [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) as an alternative to Ingress NGINX. This release includes endpoint visibility in the Dashboard, sleep/wake support, private endpoints, error page handling, and Docker Compose endpoint translation. Gateway API is behind a feature flag — Ingress NGINX remains the default and continues to work as-is. Customers opting in will need a supported gateway controller installed (Envoy Gateway recommended) <!-- 9961, 9971, 9976, 9985, 9989, 10014 --> |
There was a problem hiding this comment.
Had drafted this, but we can remove and use for next release
There was a problem hiding this comment.
I wouldn't mention it yet in the release notes, but we can specifically talk to some customers interested on it, so they can start testing it
| ### New Features {#new-features-1.42} | ||
|
|
||
| - **Build Queue Enabled by Default**: The [build queue system](core/build-service.mdx#build-queue-system) introduced as opt-in in 1.41 is now enabled by default. Build requests are automatically routed to the optimal Okteto Build pod based on real-time metrics, and when all build pods are busy, builds enter a queue to ensure consistent performance. Customers on significantly older CLI versions will continue using the legacy build path automatically. If you need to opt out, set the admin variable `OKTETO_BUILD_QUEUE_ENABLED` to `false` via [Admin Variables](admin/dashboard.mdx#admin-variables) | ||
| - **Gateway API Support (Preview)**: Added initial support for [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) as an alternative to Ingress NGINX. This release includes endpoint visibility in the Dashboard, sleep/wake support, private endpoints, error page handling, and Docker Compose endpoint translation. Gateway API is behind a feature flag — Ingress NGINX remains the default and continues to work as-is. Customers opting in will need a supported gateway controller installed (Envoy Gateway recommended) <!-- 9961, 9971, 9976, 9985, 9989, 10014 --> |
There was a problem hiding this comment.
I wouldn't mention it yet in the release notes, but we can specifically talk to some customers interested on it, so they can start testing it
| - **Persistent Namespace and Preview Indicators**: Namespaces and Preview Environments marked as [persistent](core/namespaces.mdx#mark-a-namespace-as-persistent-to-prevent-it-from-sleeping-and-deletion) now display a visual indicator in both the Okteto Dashboard and the CLI (`okteto namespace list` and `okteto preview list`), making it easier to identify which environments are exempt from automatic sleep and garbage collection <!-- 9986 --> | ||
| - Updated the Deploy dialog UI with a new drawer design for improved consistency across the Dashboard <!-- DEV-1263 --> | ||
|
|
||
| ### Deprecation Notice {#deprecation-notice-1.42} |
There was a problem hiding this comment.
Deprecation notice is always the first element to show in the release notes
| - **Build Queue Enabled by Default**: The [build queue system](core/build-service.mdx#build-queue-system) introduced as opt-in in 1.41 is now enabled by default. Build requests are automatically routed to the optimal Okteto Build pod based on real-time metrics, and when all build pods are busy, builds enter a queue to ensure consistent performance. Customers on significantly older CLI versions will continue using the legacy build path automatically. If you need to opt out, set the admin variable `OKTETO_BUILD_QUEUE_ENABLED` to `false` via [Admin Variables](admin/dashboard.mdx#admin-variables) | ||
| - **Gateway API Support (Preview)**: Added initial support for [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) as an alternative to Ingress NGINX. This release includes endpoint visibility in the Dashboard, sleep/wake support, private endpoints, error page handling, and Docker Compose endpoint translation. Gateway API is behind a feature flag — Ingress NGINX remains the default and continues to work as-is. Customers opting in will need a supported gateway controller installed (Envoy Gateway recommended) <!-- 9961, 9971, 9976, 9985, 9989, 10014 --> | ||
|
|
||
| ### Improvements {#improvements-1.42} |
There was a problem hiding this comment.
Should we also mention explicitly the renaming of keep awake to persistent? Is that relevant for the final users?
| ### Improvements {#improvements-1.42} | ||
|
|
||
| - **Persistent Namespace and Preview Indicators**: Namespaces and Preview Environments marked as [persistent](core/namespaces.mdx#mark-a-namespace-as-persistent-to-prevent-it-from-sleeping-and-deletion) now display a visual indicator in both the Okteto Dashboard and the CLI (`okteto namespace list` and `okteto preview list`), making it easier to identify which environments are exempt from automatic sleep and garbage collection <!-- 9986 --> | ||
| - Updated the Deploy dialog UI with a new drawer design for improved consistency across the Dashboard <!-- DEV-1263 --> |
There was a problem hiding this comment.
Yeah, I think it might be a good idea. We might to revisit also the docs, as we have some screenshot of the deploy dialog like: https://www.okteto.com/docs/admin/private-repositories/ssh-key/#deploy-a-private-repository
|
|
||
| ### Bug Fixes {#bug-fixes-1.42} | ||
|
|
||
| - |
There was a problem hiding this comment.
There is a small fix in the chart. We fixed a panic in the API that happened in very rare situations where a kubernetes resource was restarting and an error message wasn't being indicated by Kubernetes. That was provoking a restart in the API container
2 participants
No description provided.