Deploy your Okteto instance
Create the Okteto Namespace
Run the command below to create a namespace for okteto:
$ kubectl create namespace okteto
Configuration file
Before running helm install
, we recommend that you create a yaml configuration file with your choices about how to install Okteto. This guide will walk you through the most common options. A complete list of configuration options is available here.
You can use this sample configuration file as a starting point. The different configuration settings are explained below.
Email
You'll need to provide the email of the application owner.
email: "admin@example.com"
Cluster Endpoint
This is the public endpoint of your Kubernetes cluster. It will be used by Okteto when generating Kubeconfig
credentials for your users.
cluster:
endpoint: "https://52.30.32.1"
Domain
The domain (or subdomain) managed by your Okteto installation.
Your users will be able to access your Okteto instance at okteto.$SUBDOMAIN
. All ingresses created by okteto will be use it as well (e.g. https://app-$NAMESPACE.$SUBDOMAIN)
subdomain: "example.com"
License
Okteto is free for small teams. You get all the features of Okteto for up to 3 users.
license: XXXXX
Want to use Okteto with a bigger team? Let's talk
You can also use a secret to store the license.
Authentication
Okteto supports using Bitbucket, GitHub, Google, or OpenID Connect as authentication providers.
Use the clientId
and clientSecret
that you created in the previous step.
- Bitbucket
- GitHub
- OpenID Connect
auth:
bitbucket:
enabled: true
clientId: OAuth Consumer Key
clientSecret: OAuth Consumer Secret
workspace: my-workspace
An empty workspace
field allows any Bitbucket user to authenticate.
auth:
google:
enabled: true
clientId: clientid.apps.googleusercontent.com
clientSecret: clientSecret
auth:
github:
enabled: true
clientId: clientID
clientSecret: clientSecret
organization: my-org
An empty organization
field allows any GitHub user to authenticate.
auth:
openid:
enabled: true
clientId: clientID
clientSecret: clientSecret
group: my-group
endpoints:
issuer: https://your-provider
authorization: https://your-provider/authorization
An empty group
field allows any user to authenticate.
The issuer
and authorization
endpoints must match the value returned in the provider config discovery.
Further configuration settings are described here.
You can also use a secret to store the sensitive part of these credentials.
Deploy the Okteto Chart
Run helm install
to deploy your Okteto instance. In this example, we have named our Helm release okteto.
$ helm repo add okteto https://charts.okteto.com
$ helm repo update
$ helm install okteto okteto/okteto -f config.yaml --namespace=okteto
You can also use --version version
if you would like to install a specific version of Okteto.
Check the status of the deployment by running helm status okteto
.
Post Install Configuration
Once the chart is installed, follow the onscreen instructions to finalize the configuration.
Initial login
You can access your Okteto instance by going to https://okteto.$SUBDOMAIN. An account will be automatically created for you as part of the login process.