Archived Release Notes
Here you can find the release notes for archived versions of Okteto.
1.16.2
17 January 2024
This version is compatible with Kubernetes versions 1.25 to 1.28.
Bugfixes
- Fixed a scenario where node container runtimes could restart if the Okteto daemon pod were to be recreated, potentially impacting active 'okteto up' sessions.
1.16.1
10 January 2024
This version is compatible with Kubernetes versions 1.25 to 1.28.
Bugfixes
- The Okteto CLI used for Pipeline installation has been upgraded to version 2.23.3. It includes a fix for scenarios where image builds were failing because an image was not being found in the global registry.
- The Okteto Insights endpoint was not exposing build metrics when the Helm release name included the word "okteto"
1.16.0
20 December 2023
This version is compatible with Kubernetes versions 1.25 to 1.28.
Features
- Add
okteto_usage_build_duration_secondsbuild metrics to okteto insights. More info here - A diagnostics tool is now provided to help troubleshoot installations. More info here
- The Okteto CLI used for Pipeline installation has been upgraded to version 2.23.1
- Move garbage collection of
okteto upbased on last synced file behind a feature flag. More info here - Okteto now runs in ARM architecture. This is currently in beta.
Improvements
- Okteto garbage collector cronjob now resolves buildkit and ingress hosts to their internal IPs
- Registry Credentials cronjob only update dockerconfig secret if the credentials change.
- Okteto Daemon now update kubelet docker config.json file in nodes reactively when the static docker config secret changes. Bumps okteto/daemon to 0.5.1
- Fix network policies configuration to limit buildkit access to the nginx controller
- Add Okteto Insights Token to the Admin UI
- Updated documentation structure to make content easier to navigate and find. Release notes can now be found at https://www.okteto.com/docs/release-notes, and chart values reference can be found at https://www.okteto.com/docs/reference/helm-chart-values/. All documentation changes are listed here.
1.15.1
1 December 2023
This version is compatible with Kubernetes versions 1.25 to 1.27.
Bugfixes
- Fix okteto daemon restart when AWS ECR private registry credentials are defined
1.15.0
22 November 2023
This version is compatible with Kubernetes versions 1.25 to 1.27.
Removal Notice
Kubernetes 1.24 is no longer supported
Improvements
- Upgrade ingress-nginx to 1.9.4 (Helm chart version 4.8.3)
- Enabled chroot mode by default in both ingress-nginx controllers managed by Okteto.
okteto upsessions are now garbage collected if no files have been synced for an hour
Bug Fixes
- Fallback to default branch for destroy installer jobs
- Smart builds work on repositories using
.gitmodulescontaining submodules cloned via ssh key - Fix wrong "Scale to Zero Period" value in the UI of Admin → Namespaces
Features
- The Okteto CLI used for Pipeline installation has been upgraded to version 2.22.3
1.14.3
1 December 2023
This version is compatible with Kubernetes versions 1.25 to 1.27.
Bugfixes
- Fix okteto daemon restart when AWS ECR private registry credentials are defined
1.14.2
8 November 2023
This version is compatible with Kubernetes versions 1.24 to 1.27.
Bugfixes
- Fix private registry credentials integration for registries with custom ports (other that the default 443)
1.14.1
27 October 2023
This version is compatible with Kubernetes versions 1.24 to 1.27.
Improvements
- Okteto internal registry is now resolved in private credentials exchange
Bugfixes
- Namespace list in the UI is now scrollable and displays all namespaces.
- Fix login with openid through the okteto CLI with custom "audience" and "resource"
1.14.0
25 October 2023
This version is compatible with Kubernetes versions 1.24 to 1.27.
Deprecation Notice
- Helm charts catalog is no longer available in the Okteto UI. For alternative approach to deploy Helm charts see https://www.okteto.com/blog/making-your-helm-packaged-applications-ready-for-cloud-native-development-with-okteto/
- Defining Private Registry credentials in Helm has been deprecated. Private Registry Credentials are now natively supported by Okteto and configurable in the Okteto UI. Credentials defined in Helm will be automatically migrated.
- Support for Kubernetes 1.24 has been deprecated and will be removed in the next release.
Features
- Added a new
/metricsendpoint to expose prometheus node metrics data. More info here. - Added native support for Private Registry Credentials, configurable directly in the Okteto UI. More info here.
- The Okteto CLI used for Pipeline installation has been upgraded to version 2.21.0
- Add support for Kubernetes 1.27
Improvements
- Upgrade ingress-nginx to 1.8.2 (Helm chart version 4.7.2)
Bugfixes
- Reduce file permission for okteto-ca-pemstore certificate file in jobs
- Reduce expiration threshold for trial licenses from 60 to 7 days
1.13.0
27 September 2023
This version is compatible with Kubernetes versions 1.24 to 1.26.
Breaking Changes
Okteto requires you to use a valid license as part of the installation. If you were running a previous version of Okteto and you don't have a valid license, signup for our Free Tier (5 seats, 1 year) or reach out to us.
Improvements
- Updates to Cloud Secret now take immediate effect
- The Okteto CLI used for Pipeline installation has been upgraded to version 2.20.0
- Pipeline installations now use dynamic kubernetes tokens to talk to the kubernetes api via the ClientAuthentication API.
Bugfixes
- Documentation now links the exact version version in the docs
- During installation/upgrade the current version of Okteto is no longer tied to Helm
.Chart.Versionand.Chart.AppVersion - Improve platform and kubernetes version attributes resolution in Telemetry cronjob
1.12.1
14 September 2023
This version is compatible with Kubernetes versions 1.24 to 1.26.
Bugfixes
- Update Kubernetes internal dependencies to fix a possible crash/panic when Okteto lists the cluster API Resources. This could happen when destroying the content of a namespace or during Preview Environment operations.
- Includes the following commit from
kubernetes/client-go: https://github.com/kubernetes/client-go/commit/5ebee1886e7bc6891833dd92c200f4f5258889c0.
- Includes the following commit from
1.12.0
31 August 2023
This version is compatible with Kubernetes versions 1.24 to 1.26.
Breaking changes
- Kubeconfigs downloaded from the Okteto web UI now require Okteto CLI 2.15 or higher to use dynamic tokens for authenticating against Kubernetes.
Features
- The Okteto CLI has been upgraded to version 2.19.2.
- The Admin view has been redesigned with a new vertical tab column.
- Added "Registry Credentials" to the Admin view to display configured private registry information. This provides visibility into the private registries in use for your Okteto instance (username/password and AWS Access/Secret only for now)
Improvements
- The Preview list in the Admin view now shows time units in the Garbage Collector settings description.
- When waking a Namespace from the Namespace, Preview, or Admin views, the UI now provides feedback for the request.
- When a GitHub user does not belong to the allowed GitHub organization and attempts to log in, a specific error is now shown.
- When using a GitHub App for authentication that is not yet installed in the GitHub organization and an allowed GitHub organization filter is set, a specific error is now shown.
- Resources for Nodes in the Admin view are now correctly aligned.
- Priority Classes can now be specified via
priorityClassNamesub-property for the following components:api,buildkit,defaultBackend,frontend,registryandwebhook.
1.11.1
8 August 2023
Bugfixes
- When deploying compose files, Okteto built-in environment variables (e.g OKTETO_BUILD_XXX) were not expanded correctly.
1.11.0
2 August 2023
Improvements
- Upgraded buildkit to v0.11.6.
- Upgraded ingress-nginx to 4.7.1.
- Underlying Kubernetes cluster version is now shown in the Admin section.
- When a GitHub App private key is not valid, a warning message is now shown in a components' logs and when attempting to authenticate or perform a GitHub-related action.
- Okteto Web UI documentation links now point to the same version used by the platform instead of the latest version.
- Automatic role binding for service accounts can now be disabled.
- Added configuration setting in the daemonset to disable the configuration of private registry credentials in the nodes
Bugfixes
- When hovering over logs in the Okteto Web UI, a wrong timestamp was shown.
- Istio's Virtual Service now show only their own dedicated endpoints when using "dev.okteto.com/endpoints" annotation.
1.10.0
5 July 2023
Removal Notice
Kubernetes 1.23 is no longer supported.
Features
- Kubernetes supported versions: 1.26, 1.25 and 1.24.
- Now you can select an expiration period when creating a new Personal Access Token.
- Administrators have the ability to wake up, put to sleep, or mark any preview environment as keep-awake.
- Upgraded ingress-nginx to 4.6.
Improvements
- Kubernetes Annotations can now be added to:
- Default self-signed wildcard certificate via
.Values.wildcardCertificate.annotations. - Internal self-signed webhook certificate via
.Values.webhook.internalCertificate.annotations. - Dockerconfig via
.Values.secret.annotations.
- Default self-signed wildcard certificate via
- Kubernetes Labels can now be added to:
- Dockerconfig via
.Values.secret.labels.
- Dockerconfig via
Bugfixes
- When using the default
.Values.subdomain, pending Domain installation task is now correctly shown. - Cert-manager annotations are now allowed in developer ingresses.
- When a license is not specified, the Starter plan is displayed instead of Unknown.
- Upgraded the Okteto CLI version to 2.16.5.
- When using
okteto deploy --remote ...with private certificates, internal registry requests will now work correctly.
- When using
- We've added additional form validation to the Launch Dev Environment modal so invalid repo URLs will no longer be accepted and allow the modal to close.
- Pipeline destroy actions now use the environment variables used during deployment.
1.9.1
22 June, 2023
Bugfixes
- Upgrade ingress-nginx from 4.5.0 to 4.5.2 to include the following bugfix:
- Fix regression when using regex in ingress path https://github.com/kubernetes/ingress-nginx/issues/9616
1.9.0
12 June, 2023
Deprecation Notice
- Support for Kubernetes 1.23 has been deprecated and will be removed in the next release.
Features
- Added support for Kubernetes v1.26. All supported versions: 1.26, 1.25 and 1.24.
- Upgraded the Okteto CLI version to 2.16.3
- Last user interaction with Okteto is now available at the Admin dashboard, under the Users section.
- Support to access Okteto on
127.0.0.1 - Upgrade ingress-nginx to 4.5
okteto deploy --remotesupports when Okteto has self-signed certificates and private Certificate Authorities (CAs).
Improvements
- Enabled gzip compression for frontend web server
Bugfixes
- Improve app chunk loading and error handling
- Uninstall Helm installations from dev environments on "destroy all" operations
- Deactivate any containers in development mode on "sleep namespace" operation
- Environment variables defined for a deploy are also available for destroy operation
- Container image layer manifest sometimes got corrupted when being uploaded to the Registry, causing "500 Internal Server Error" on following build requests to Buildkit.
- When using dual ingress controller (default), requests body size was limited to 1MiB. This has been fixed and increased to 60MiB.
1.8.3
15 Jun, 2023
Bugfixes
- When using dual ingress controller (default), requests body size was limited to 1MiB. This has been fixed and increased to 60MiB.
1.8.2
30 May, 2023
Bugfixes
- Upgraded the Okteto CLI version to 2.15.4.
- Build optimization now also considers the environment variables used in build args when determining when to rebuild an image.
1.8.1
24 May, 2023
Bugfixes
- Fixed an issue affecting deletion of dev and preview environments when using custom Okteto manifests. The destroy operation did not evaluate the custom manifest used during deployment, which meant the destroy commands were not executed.
- Upgraded the Okteto CLI version to 2.15.3.
- Build optimization now considers environment variables used in build args to determine when to rebuild an image.
- Fixed a regression which was preventing the deploy dialog from loading the list of GitHub repositories for new users when the authentication provider was GitHub.
1.8.0
10 May, 2023
Before you upgrade
Okteto 1.8 includes a change in the ingress architecture. If you're using your own ingress controller instead of the ingress-controller embedded with Okteto chart, please checkout the updated section about "How to use your own ingress controller".
Breaking changes
- The default value for the buildkit service session affinity is now
None. To keep usingClientIPassessionAffinityyou need to setservice.sessionAffinity: ClientIPin your buildkit configuration.
Deprecation Notice
- Support for Kubernetes 1.22 has been deprecated and will be removed in the next release.
Features
- Kubernetes supported versions: 1.25 (upgrade guide), 1.24 and 1.23.
- Support for custom labels and annotations in ingresses managed by Okteto.
- Upgraded the Okteto CLI version to 2.15.2
- Okteto CLI 2.15.2 enables the optimization removed at Okteto CLI 2.14.3. Now we calculate a hash for a given commit with the info around the build.
- Okteto Self-Hosted will now show the installation setup guide by default
- External resources can now be destroyed from the Okteto UI
- External resources now supports additional icons
- Ingresses are now served through two ingress-controllers instances, enabling flexible configuration and improving connection stability.
ingress-nginxwill continue to be the main gateway for all inbound traffic to Okteto, but will stop processing individual users' ingresses. Instead it will forward users' ingresses to the newokteto-nginx.okteto-nginxsits behindingress-nginxand it process exclusively users' ingresses.- For additional configuration of both instances, please check the ingress-controller configuration section.
- Okteto Ingress defaultBackend is now deployed separately of
ingress-nginxorokteto-nginx.
Improvements
- All external services created or updated by Okteto will now have the
dev.okteto.com/namespacelabel - Improved the performance of the query for retrieving endpoints for a preview environment using the
dev.okteto.com/namespacelabel - Support baggage header for istio divert driver
- Remove the
emailfield from the helm values file. It is is now provided by the license - Divert virtual service transformation is now done at the mutation webhook by adding the annotation to the virtualservices
- The frontend app now uses proper browser history routing instead of hash routing
- Catalog items are now sorted, by default, in the same way in both the admin dashboard and a developer's deploy/redeploy modal
- Using personal repositories from Bitbucket is now possible as we've addressed an issue with restricted characters in repository names
- Persistent spaces can no longer be put to sleep from the admin dashboard
- Improve text readability on deploy resources list
Bugfixes
- Custom endpoints annotation
dev.okteto.com/endpointsis now mapped with the correct service of an ingress - Fix preview delete confirm modal stating "Delete namespace"
- Tabs in the admin panel are now appropriately responsive for smaller screens and resolutions. The last tabs will now wrap properly
- External Resources markdown inline code is now rendered correctly as inline instead of a fenced code block
- Translation browser extensions causing blank screens due to modifying DOM
- Show endpoints coming from virtual services in the Preview List view
- Move cache headers from
metato nginx soCache-Controlheaders are applied correctly - Show "managed by" message only when adding a repository to previews and not when launching a development environment
- Force non-breaking spaces for leading whitespace on logs
- Fix panic produced when deploying a repository with trailing slash
- Add disable state to external resources when being destroyed
1.7.1
21 April, 2023
Bugfixes
- Upgraded the Okteto CLI version to 2.14.3.
- Okteto CLI 2.14.0 introduced an optimization to build only once the image for a given commit. Okteto CLI 2.14.3 disables this optimization while we fix some inconsistencies around its behavior
1.7.0
12 April, 2023
Removal Notice
- Kubernetes 1.21 is no longer supported.
Deprecation Notice
The cloud.provider and cloud.secret keys in the Helm chart are now deprecated and they will be removed in the future 2.x release. Instead, you can now use registry.storage.provider and registry.secret to configure the registry to use external storage. This change is backward compatible: the old configuration keys will continue to work until they are removed in 2.x. You can follow our upgrade guide.
Features
- Kubernetes supported versions: 1.24, 1.23 and 1.22.
- Support for the annotation dev.okteto.com/endpoints to customize the endpoints shown in the Okteto UI.
- Support for configuring the service account of buildkit.
- Support for token-based authentication to simplify the installation of Okteto Self-Hosted.
- Personal Access Tokens will automatically expire after 180 days. For existing tokens, the expiration date will be set to 180 days from when your Okteto instance is upgraded to 1.7 or newer versions
- Upgraded the Okteto CLI version to 2.14.2
- Upgraded ingress-nginx to 4.3.0
- You can now delete external resources from the UI
- The default installation of Okteto doesn't require an external storage for the registry. It now uses filesystem storage by default
- The default installation of Okteto doesn't require a PVC for BuildKit. It now uses filesystem storage by default
Improvements
- When
buildkit.ingress.enabledis true, BuildKit is exposed in thebuildkit.service.portinstead of port 1234. This makes it easier to use your with other ingress controllers - We optimized the redeploy dialog experience. Information loads faster in the dialog, specially when the source is GitHub
- Improved confirmation dialogs messages
- When your Okteto instance doesn't have an auth provider configured, the login screen shows a message with a link to the documentation on how to configure it
- Pod Security Policies are not installed if they are not available in the cluster