Okteto 1.8 Chart Release, CLI 2.16 and Support for Kubernetes 1.25
We're excited to bring you another product update with several great new features and improvements to the Okteto experience.
- Okteto 1.8 Chart Release
- Change to ingress architecture that affects customers using their own ingress-controller
- Okteto CLI 2.16 Release
- Support for Kubernetes 1.25
- Dropped support for Kubernetes 1.22
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".
The latest version of the Okteto CLI includes several new features and some bug fixes. You can find a more thorough overview of what's new in versions 2.15 and 2.16 in our documentation link below.
As part of our goal to maintain N-2 version support for Kubernetes, we've now added support for v1.25 to remain aligned with cloud infrastructure providers and the regular channel releases from the CNCF and Kubernetes community.
We've added an in-app experience to the Okteto Admin UI showing the main steps in the Okteto installation process. You now have a source of truth within the Admin UI to gather necessary access credentials or other information to get Okteto installed within your environment even faster than before.
Each step in the guide is optional and can be skipped if it does not apply to your situation and provides documentation to help complete the step to ensure success with the process.
You can now manually destroy External Resources from the Okteto UI that you provisioned as part of your deploy configuration, in the Okteto manifest, to ensure those resources don't remain active and idle when development of your application is complete.
We've added additional icons to External Resources to improve the developer experience when interpreting the resources that are part of an application in Okteto. New icons include:
Previously the two Catalog modals were sorted differently. Now both the admin and developer views should be defaulted sorted in the same way: alphabetically.
We've improved the integration with Bitbucket to now support personal repositories. This gives customers an additional option to bring code repositories into Okteto for faster development.
We've removed the option for admins to sleep a namespace that had been set to Keep Awake previously. This ensures that when a namespace is intended to persist garbage collection it cannot still be put in a sleep state and cause a confusing experience for developers of that namespace.
This value has changed to None by default and will break your Okteto experience if you do not make a change to your buildkit configuration.
To keep using ClientIP as sessionAffinity you must set service.sessionAffinity: Client IP in your buildkit configuration.
For a more detailed list of improvements, bug fixes, breaking changes, and deprecation notices please see our documentation.