Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
翻訳待ち
Okteto gives coding agents production-like environments to verify their work. Isolated, full-stack, on your infrastructure. Tested code, not guesses
翻訳待ち
開発ツールGo · ShellGitHub @oktetoオンライン所有者未確認
Have you tried it? One tap is enough. No sign-in needed.
Develop your applications directly in your Kubernetes Cluster
翻訳待ち
Loading the full README.
Read the full README ↗Kubernetes has made it very easy to deploy applications to the cloud at a higher scale than ever, but development practices have not evolved at the same speed as application deployment patterns.
Today, most developers try to either run parts of the infrastructure locally or just test their integrations directly in the cluster via CI jobs, or the docker build/redeploy cycle. It works, but this workflow is painful and incredibly slow.
okteto accelerates the development workflow of Kubernetes applications. You write your code locally and okteto detects the changes and instantly updates your Kubernetes applications.
Okteto enables development inside a container, providing a seamless IDE and tool integration as if you were working locally but with the resources of a remote cluster. When you run okteto up your Kubernetes deployment is replaced by a Development Container that contains your development tools (e.g. maven and jdk, or npm, python, go compiler, debuggers, etc). This development container can use any docker image. The development container inherits the same secrets, configmaps, volumes or any other configuration value of the original Kubernetes deployment.
The end result is a remote cluster that is seen by your IDE and tools as a local filesystem/environment. You keep writing code on your local IDE and as soon as you save a file, the change goes to the development container, and your application instantly updates (taking advantage of any hot-reload mechanism you already have). This whole process happens in an instant. No docker images need to be created and no Kubernetes manifests need to be applied to the cluster.
okteto has several advantages when compared to more traditional development approaches:
okteto decouples deployment from development. You can deploy your application with kubectl, Helm, a serverless framework, or even a CI pipeline and use okteto up to develop it. This is especially useful for cloud-native applications where deployment pipelines are not trivial.okteto works with any Kubernetes cluster, local or remote. okteto is also available for macOS, Linux, and Windows.All you need to get started is to install the Okteto CLI and have access to a Kubernetes cluster. You can follow our guide for setting up a Kubernetes cluster on AWS here.
The Okteto Open Source CLI requires access to a Kubernetes cluster. The Okteto Open Source CLI aims to enable you to develop your cloud-native applications using Development Containers in your Kubernetes clusters. If you are interested in helping your entire team share a Kubernetes cluster for development, we recommend you check out our commercial product, the Okteto Platform
The Okteto Open Source CLI supports the following commands:
okteto contextokteto upokteto down[!NOTE] ⚠️ Notice: The open-source version of Okteto only supports the dev section of the Okteto manifest. For additional features and full functionality, consider exploring the Okteto Platform.
We have getting started guides for the Open Source mode for the following languages:
The Okteto Platform CLI requires the installation of the Okteto Helm Chart in your Kubernetes cluster. In this mode, all the Okteto CLI commands are available (build, deploy, up, down, destroy, etc). The Okteto Platform comes with additional features like:
This is the beginning of the README. Read the rest at the original. Read the full README ↗