The email of the application owner.
endpoint: The public endpoint of your Kubernetes cluster. It will be used by Okteto when generating
Kubeconfigcredentials for your users.
Okteto is free for small teams. You can manage up to 3 users without having to provide a license.
Want to use Okteto with a bigger team? Let's talk
You can also use a secret to store the license.
The domain (or subdomain) managed by Okteto.
Your Okteto instance will be available at
okteto.$SUBDOMAIN. All ingresses created by okteto will use it as well (e.g. https://app-$NAMESPACE.$SUBDOMAIN)
After installation, we recommend that you create a DNS entry for
*.$SUBDOMAIN, pointing to the public address of your load balancer.
Okteto supports using Bitbucket, GitHub, Google, or OpenID Connect as authentication providers.
You can also use a secret to store the sensitive part of these credentials.
Follow Bitbucket's official documentation on how to create an OAuth Consumer.
When creating the OAuth Consumer, you will need to provide the following values:
Permissions: Account: Email Account: Read
Use this group of settings when using Bitbucket OAauth as your authentication provider.
clientId: OAauth Consumer Key
clientSecret: OAauth Consumer Secret
workspace field is optional. Only members of the workspace will be allowed to login into your Okteto instance. An empty
workspace field permits any user to log in.
Follow GitHub's official documentation on how to create an OAuth App.
When creating the OAuth App, you will need to provide the following values:
Authorization callback URL:
Use this group of settings when using GitHub OAuth as your authentication provider.
organization field is optional. Only members of the organization will be allowed to log in into your Okteto instance. An empty
organization field permits any user to log in.
Follow Google's official documentation on how to create an OAuth 2.0 Client.
When creating the OAUTH 2.0 Client, you will need to provide the following values:
Authorized redirect URIs:
Use this group of settings when using Google OAuth as your authentication provider.
Follow your OpenID Connect service provider's documentation on how to create the required application.
When creating the application, you'll need to provide the following values:
- Start SSO URL:
- Redirect URIs:
- Response Type:
- Grant Type:
Use this group of settings when using an OpenID Connect provider as your authentication provider.
group field is optional. Only members of the group will be allowed to log in into your Okteto instance. An empty
group field permits any user to log in.
authorization endpoints must match the value returned in the provider config discovery.
mapping fields are optional. Use them to configure the mapping between Okteto's user attributes and the claim coming from your authentication provider.
Your provider needs to support the UserInfo endpoint in order to be used with Okteto. This authentication option follows the OpenID standard, and it has been validated with Okta, PingIdentity, and GitLab.
Okteto integrates with different cloud providers to store the Okteto Registry images.
The sensitive part of the credentials are not included in the configuration file. Instead, it is provided to Okteto via a secret.
Use this to use Azure Storage to store your private images.
container: "Storage Container Name"
accountName: "Storage Account Name"
The storage setting will be used by the registry to pull and push images (if using cloud storage). This needs to be created before installing Okteto.
Use this to use S3 to store your private images.
bucket: "Bucket Name"
region: "AWS region"
accessKeyID: "IAM Access Key"
The bucket will be used by the registry to pull and push images (if using cloud storage). This needs to be created before installing Okteto.
Use this to use DigitalOcean Spaces to store your private images.
The space settings will be used by the registry to pull and push images (if using cloud storage). This needs to be created before installing Okteto.
Use this to use Google Cloud Storage to store your private images.
bucket: "Bucket Name"
project: "Project ID"
The bucket settings will be used by the registry to pull and push images (if using cloud storage). This needs to be created before installing Okteto.
Use this if you're using a provider not currently supported by Okteto.
byo you'll need to configure your registry to use the file system for storage.
Advanced Cloud Scenarios
It is possible to use separate cloud providers for DNS than for storage if needed. Reach out to support, we're always happy to help!
The API service. Account and Kubernetes credentials management, namespace creation, and sharing, deployment via the catalog, etc...
annotations: Annotations to add to the API pods.
extraEnv: Environment variables to be set on the API containers.
labels: Labels to add to the API pods.
replicaCount: The number of API pods. It defaults to 2.
resources: The resources for the API pods.
- name: NO_PROXY
The cluster autoscaler service. Disabled by default.
It instructs the Kubernetes cluster autoscaler to scale nodes if the real cpu/memory usage of a node is beyond the limits.
tolerations.devPool to limit the autoscaler analysis to a subset of cluster nodes.
Requirements: cluster autoscaler and metrics server must be installed in your cluster.
annotations: Annotations to add to the autoscaler pods.
cpu.up: Increase the cluster size when the CPU consumption is greater than or equal to this value. It defaults to 60 percent.
cpu.down: Decrease the cluster size when the CPU consumption is lesser than this value. It defaults to 40 percent.
increment: The number of new nodes to request when all the current nodes are overloaded. e.g. if this value is 3, the autoscaler will request 3 new nodes when all the cluster nodes are overloaded. It defaults to 1.
labels: Labels to add to the autoscaler pods.
max: Maximum number of nodes in the cluster. It defaults to 10. Zero means unlimited.
memory.up: Increase the cluster size when the Memory consumption is greater than or equal to this value. It defaults to 70 percent.
memory.down: Decrease the cluster size when the Memory consumption is lesser than this value. It defaults to 50 percent.
min: Minimum number of nodes in the cluster. It defaults to 1.
nodePoolLabel: The node label that identifies the node pool of the node. For example, the value in GKE is
cloud.google.com/gke-nodepool. In EKS the value is
eks.amazonaws.com/nodegroup. If set, the autoscaler scales each node pool independently.
pods.up: Increase the cluster size when the Pods in a node vs the max pods per node is greater than or equal to this value. It defaults to 90 percent.
pods.down: Decrease the cluster size when the Pods in a node vs the max pods per node is lesser than this value. It defaults to 80 percent.
schedule: How often, in seconds, the autoscaler analyzes if the cluster needs to be scaled. It defaults to 300.
slackWebhook: A slack webhook url to notify autoscaler events.
volumes.up: Increase the cluster size when the Volumes in a node vs the max volumes per node is greater than or equal to this value. It defaults to 90 percent.
volumes.down: Decrease the cluster size when the Volumes in a node vs the max volumes per node is lesser than this value. It defaults to 80 percent.
The build service. It's used in combination with
okteto build to build containers directly in the cluster.
annotations: Annotations to add to the buildkit pods.
extraEnv: Environment variables to be set on the buildkit containers.
hpa.enabled: Enable horizontal pod autoscaling for the buildkit pods. Disabled by default.
hpa.min: Minimum number of buildkit pods to keep running.
hpa.max: Maximum number of buildkit pods to scale to.
hpa.cpu: The amount of CPU utilization that will cause the HPA to scale the buildkit pods.
labels: Labels to add to the buildkit pods.
podManagementPolicy: The podManagementPolicy of the buildkit pods. Defaults to
replicaCount: The number of buildkit pods. It defaults to 1.
resources: The resources for the buildkit pods.
storage.class: The storage class of the volume attached to every buildkit pod to persist the buildkit cache.
storage.size: The size of the volume attached to every buildkit pod to persist the buildkit cache.
storage.cache: The size of the buildkit cache to store image caches. It should be 30Gi smaller than
- name: NO_PROXY
In order to handle timeouts during communication between the client and the buildkit daemon, the following environment variables can be modified on the server side:
OKTETO_KEEPALIVE_SERVER_TIME_MS: After this duration of time, if the server doesn't see any activity it pings the client to see if the transport is still alive. If set below 1s, a minimum value of 1s will be used. The current default value is 2 hours.
OKTETO_KEEPALIVE_SERVER_TIMEOUT_MS: After having pinged for keepalive check, the server waits for a duration of Timeout and if no activity is seen, the connection is closed. The current default value is 20 seconds.
OKTETO_KEEPALIVE_SERVER_MAX_CONN_IDLE_MS: Duration for the amount of time after which an idle connection would be closed by sending a GOAWAY. Idleness duration is defined since the most recent time the number of outstanding RPCs became zero or the connection establishment. The current default value is infinity.
OKTETO_KEEPALIVE_SERVER_MAX_CONN_AGE_MS: Duration for the maximum amount of time a connection may exist before it will be closed by sending a GOAWAY. A random jitter of +/-10% will be added to the value to spread out connection storms. The current default value is infinity.
OKTETO_KEEPALIVE_SERVER_MAX_CONN_AGE_GRACE_MS: An additive period after
OKTETO_KEEPALIVE_SERVER_MAX_CONN_AGE_MSafter which the connection will be forcibly closed. The current default value is infinity.
OKTETO_KEEPALIVE_SERVER_POLICY_MINTIME_MS: Minimum amount of time a client should wait before sending a keepalive ping. The current default value is 5 minutes.
OKTETO_KEEPALIVE_SERVER_POLICY_PERMIT_WITHOUT_STREAM: If true, server allows keepalive pings even when there are no active streams(RPCs). If false, and client sends pings when there are no active streams, server will send GOAWAY and close the connection. False by default.
The daemonset automatically configures every node of your cluster to work better with Okteto.
annotations: Annotations to add to the daemonset pods.
extraEnv: Environment variables to be set on the daemonset containers.
labels: Labels to add to the daemonset pods.
image: Container image used by the daemonset pods.
The frontend service serves the web application.
annotations: Annotations to add to the frontend pods.
extraEnv: Environment variables to be set on the frontend containers.
labels: Labels to add to the frontend pods.
replicaCount: The number of frontend pods. It defaults to 2.
resources: The resources for the frontend pods.
- name: NO_PROXY
The garbage collector service. It automatically scales idle applications to zero and deletes unused namespaces. Enabled by default.
annotations: Annotations to add to the gc pods.
labels: Labels to add to the gc pods.
scaleToZeroPeriod: The duration, in hours, that an application or resource must be idle before the garbage collector scales it to zero. Set to zero to disable.
deleteNamespacePeriod: The duration, in days, that a namespace must be idle before the garbage collector deletes it. Set to zero to disable.
slackWebhook: If set, the garbage collector will send a notification when it scales a resource to zero or when it deletes a namespace.
The jobs that deploy your development environments from Git.
annotations: Annotations to add to the installer job pods.
extraEnv: Environment variables to be set on the installer job containers.
labels: Labels to add to the installer job pods.
image: to configure your custom installer binaries, including a custom Okteto CLI version.
runner: to configure your custom installer image.
activeDeadlineSeconds: Maximum duration of the pipeline in seconds.
gitSSHUser: User to be used when cloning git repos using ssh.
sshSecretName: The name of the secret that contains the private key used when cloning git repos using ssh. If it doesn't exist, the key and the secret will be automatically generated by Okteto.
- name: NO_PROXY
The private container registry.
annotations: Annotations to add to the registry pods.
extraEnv: Environment variables to be set on the registry containers.
ingress.annotations: Annotations to add to the registry ingress. These annotations take precendence over the ones defined in the ingress section.
ingress.tlsSecret: TLS secret for the registry endpoint. If empty, okteto will default to the wildcard certificate created by Okteto.
labels: Labels to add to the registry pods.
pullPolicy: The security policy for image pulls. If set to
cluster, any Okteto user can pull any image from the registry. When set to
namespace, only users with access to the namespace can pull images from the namespace. It defaults to
replicaCount: The number of registry pods. It defaults to 1.
resources: The resources for the registry pods.
serviceAccountName: The service account used by the registry. It defaults to
storage: The storage mechanism for the images.
cloud.enabled: Set this to true if you want to store the images using your cloud provider's block storage service (e.g. S3). It will use the values defined in the
cloudkey. It's enabled by default.
- name: NO_PROXY
filesystem: Set this to true if you want to store the images in PVC attached to the registry. This might limit your ability to scale up the registry, depending on the type of storage you are using. You can also customize the
sizeof the volume, and even attach an existing volume claim via
You can enable or disable the telemetry job. The telemetry job "phones home" once a day with the following information:
- Number of managed users
- Number of managed namespaces
- Kubernetes Version and Platform
- A unique install ID
- Your license ID.
- The name of the authentication provider
- The name of the cloud provider
Okteto uses the information to help us better understand how our customers use Okteto, as well as to help us prioritize fixes and features. We don't share your information with anyone else.
If this configuration is disabled, Okteto CLI analytics are automatically disabled.
The webhook service. Ingress creation, generation of hostnames, enforcement of policies, etc...
annotations: Annotations to add to the webhook pods.
extraEnv: Environment variables to be set on the webhook containers.
hostNetwork: Enables or disables host networking for the webhook deployment. The default is false.
labels: Labels to add to the webhook pods.
port: Port sets the port used for the webhook deployment. The default is 443.
replicaCount: The number of webhook pods. It defaults to 2.
resources: The resources for the webhook pods.
Apply default affinities to pods deployed in namespaces created by Okteto.
- weight: 10
- key: cloud.google.com/gke-preemptible
In this case, pods deployed in namespaces created by Okteto will have a preferred affinity to land on preemptible nodes.
repository: The Helm repository available for every developer. This is disabled by default. To enable, set the
applications.repositoryproperty to your Helm registry URL
Okteto assings this cluster role to every user via a namespace-scoped role binding.
The default value assigns each developer a
cluster-admin role binding with only access to their personal namespaces.
RoleBindings to be created for every user's service account. This is useful if you want to grant access to resources in other namespaces of the cluster. Disabled by default.
RoleBindings will reference
ClusterRoles and will be scoped to the
namespace specified in the configuration. Okteto will not create neither the
ClusterRoles nor the
Namespaces and expects them to exist in the cluster. Here's an example configuration:
Converts services with type LoadBalancer into ClusterIP and automatically creates an ingress. Enabled by default.
Uses the specified storage class for all persistent volume claims created when developers execute
okteto up. This setting will override any storage class defined on the Okteto manifest. Disabled by default.
storageClass: The storage class enforced for persistent volume claims created by
There is only one exception where this storage class is overwritten. In case of having volume snapshots feature configured, if a storage class is required for the snapshots that storage class will have preference.
Okteto assings this cluster role to every user via a cluster role binding. By default, this behavior is disabled. This can be useful to give access to cluster level resources to every developer account, like accessing the Node API.
Configure default values for the ingress created by Okteto.
annotations: The annotations to apply to all the ingresses created during the Okteto installation.
ingressClassNameto apply to all the ingresses created during the Okteto installation (defaults to
class: If specified, Okteto will set this as the
ingressClassNameof all ingresses managed by Okteto. This is useful if you have more than one ingress controller in your cluster.
forceIngressClass: If enabled, all ingresses deployed in namespaces managed by Okteto will have the ingress class defined in
ip: The internal IP of the ingress. Pods will call the Okteto API and the Okteto Registry using this IP. Required if the Okteto API/Registry is exposed using an ingress not managed by Okteto.
tlsSecret: TLS secret for the ingress created by Okteto. If empty, okteto defaults to the wildcard certificate created by Okteto.
Configure ingress connections limits for each public endpoint. Disabled by default.
connections: Maximum parallel connections for each ingress.
rps: Maximum requests per second for each ingress.
rpm: Maximum requests per minute for each ingress.
Automatically inject kubectl, helm, and okteto binaries on every development environment, and on the git and helm deployment pipelines. This requires permissions to mount a host volume.
If this is disabled, you'll need to provide your own image in
Annotation and label customizations for namespaces. The configured annotations and labels will be applied to each namespace created by Okteto. These annotations and labels are additional to the ones already applied by Okteto.
annotations: Annotations applied to each namespace generated by Okteto.
labels: Labels applied to each namespace generated by Okteto.
Configures network policies for each namespace to isolate network traffic. Disabled by default.
blockedCIDRs: Outgoing traffic to any cidr on this list will be blocked by the network policy (optional).
Overrides the default kernel values for file watchers in every node. Recommended if you're running databases, or if you plan on using "okteto up" on the cluster. This requires permission to mount and modify /proc values.
maxUserWatches: The maximum number of allowed inotify watchers.
maxMapCount: The maximum number of memory map areas a process may have.
aioMaxNR: The maximum number of allowable concurrent IO requests.
Overrides the registry hostname resolution to use internal IPs. This requires permission to mount and modify the cluster nodes' /etc/hosts file.
Pre-pull the git and helm installer images in all the nodes. This requires permission to mount the docker socket.
A list of private registries and its corresponding credentials. The kubelet will use them when pulling images:
tokenif your registry does not support username/password authentication (e.g. google registry).
If you are using an AWS private registry, Okteto takes care of refreshing docker credentials every 4 hours.
You can use this to configure a Docker Hub account for your cluster in order to avoid DockerHub's pull limits. Be careful, a credential misconfiguration could lead to an issue where kubelet cannot pull public images from Docker Hub. If this happens, follow these instructions to recover from this state.
PullAlways image pull policy in the cluster. Enabled by default.
The list of shortcuts to show in the "Deploy from Git Repository" dialog.
name: Name to identify the quickstart.
url: Repository URL configured for the quickstart.
branch: Default branch to be considered for the configured quickstart repository.
variables: List of variables to be passed to the pipeline on deployment time.
name: Indicates the variable name.
value: Specifies the default value.
options: Specifies an enumeration of possible values.
default: Flag to indicate if
variablesfields will be automatically filled with configured values in the "Deploy from Git Repository" dialog.
- name: "Movies Sample App"
- name: DB_HOST
- name: THEME
options: ["dark", "light"]
- name: "GitHub"
- name: "GitLab"
- name: "Bitbucket"
Enables resource quotas at the namespace level.
resources: Limits the number of resources that a user can create.
maxNamespaces: Maximum number of namespaces.
maxPods: Maximum number of pods per namespace.
maxReplicationControllers: Maximum number of replication controllers per namespace.
maxSecrets: Maximum number of secrets per namespace.
maxConfigMaps: Maximum number of config maps per namespace.
maxPVCs: Maximum number of persistent volume claims per namespace.
maxVolumeSnapshots: Maximum number of volume snapshots per namespace.
maxIngresses: Maximum number of ingresses per namespace
bandwidth: Limits the incoming/outcoming bandwidth per pod. Requires using the Okteto NGINX Ingress Controller.
ingress: Maximum ingress bandwidth.
egress: Maximum egress bandwidth.
up: Limits the incoming/outgoing bandwidth per development container.
ingress: Maximum ingress bandwidth for a development container
egress: Maximum egress bandwidth for a development container.
requests: Limits the maximum resource requests per namespace.
cpu: Maximum CPU resource requests.
memory: Maximum memory resource requests.
storage: Maximum storage resource requests.
limits: Limits the maximum resource limits per namespace.
cpu: Maximum CPU resource limits.
memory: Maximum memory resource limits.
storage: Maximum storage resource limits.
limitranges: Configures the limit ranges of each namespace.
max: Configures the maximum resources per container.
cpu: Maximum CPU resource limits.
memory: Maximum memory resource limits.
requests: Configures the default resource requests per container.
limitRequestRatio: If this value is different than zero, Okteto automatically sets the requests of each container to its limits divided by this value. It is useful to keep requests low in the cluster and make better usage of your infrastructure. Defaults to 1000.
cpu: Default CPU resource requests. Ignored if
limitRequestRatiois different than zero.
memory: Default memory resource requests. Ignored if
limitRequestRatiois different than zero.
limits: Configures the default resource limits per container.
cpu: Default CPU resource limits.
memory: Default memory resource limits.
The default values are:
Labels and annotations to include in the secret created by the chart. Useful if you want to integrate with Vault or similar secret stores.
Indicates tolerations for the okteto components.
Define the label and taint
okteto-node-pool on your worker nodes to match these values.
oktetoPool: Tolerations for the api, webhook, gc, autoscaler, ingress controller, and frontend services.
buildPool: Tolerations for the buildkit and registry services.
devPool: Tolerations for the pods deployed in namespaces created by okteto.
For example, if you add the label
okteto-node-pool:build and the taint
okteto-node-pool=build:NoSchedule to a node, and you
buildPool: build, the buildkit and registry pods are deployed to this node.
Disable if you want to enforce using the
username as a suffix on namespaces and ingress hosts. Enabled by default.
When enabled Okteto automatically adds a preferred affinity to every pod, which leans towards placing pods from the same namespace and in the same node (default:
Allows you to specify different settings for volumes.
validate: Section to configure volume validation.
enabled: Enables volume validation. Disabled by default
supportedStorageClasses: List of supported storage classes.
forceStorageClass: Flag to specify if the storage class should be enforced in case of creating a volume with a non-supported storage class. If set, the first storage class specified on
supportedStorageClasseswill be the enforced value.
supportedAccessModes: List of supported access modes.
supportedStorageClasses: ["standard", "standard-rwo"]
Enables users to initialize persistent volume claims with the contents of a preexisting volume snapshot.
This feature requires having a CSI driver installed in your cluster.
driver: The name of the CSI driver used when creating snapshots.
class: The VolumeSnapshotClass of the volume snapshot.
storageClass: The storage class required by volumes initialized from snapshots (optional).
enableNamespaceAccessValidation: When enabled, only users that have access to the namespace where the volume snapshot is stored will be able to use it in their development environments. Default false.
allowIDAnnotation: Allow using your cloud provider's snapshot ID as the source of the data. Default true.
dev.okteto.com/from-snapshot-id annotation to any persistent volume claim to tell Okteto to initialize your persistent volume claim, as shown below:
When a persistent volume claim resource is created, Okteto will import the snapshot in Kubernetes using a VolumeSnapshotContent and will set the source of your persistent volume claim to this VolumeSnapshotContent.
Disable if you want to bring your own certificates and/or certificate authority. Enabled by default.
create: If set to false, Okteto will not create the wildcard certificate automatically.
duration: The duration of the certificate. Ignored if
createis set to
name: The name of the secret where the certificate will be stored.
privateCA.enabled: Set to true when using a private certificate authority.
privateCA.secret.name: The name of the secret that stores the private certificate authority's certificate.
privateCA.secret.key: The key in the secret that stores the private certificate authority's certificate.
# if using a private CA, specify the name of the TLS secret that stores the certificate
The configured annotations and labels are additional to the ones already applied by Okteto.
annotations: Annotations added to each service account generated by Okteto for user accounts.
labels: Labels added to each service account generated by Okteto for user accounts.
A common use case for adding service account annotations is to get access via IAM Roles or Workload Identity to create Cloud resources as part of your Okteto Manifest
Okteto will automatically install NGINX Ingress Controller as part of the default installation, using its official Helm chart.
ingress-nginx keys in your configuration file to modify the configuration.
For example, to change the number of replicas, you'd need to add the following:
The full list of values is available here.