Deployment guide

Requirements

  • kubectl - Command line tool that interacts with the Kubernetes API server and is useful for managing Kubernetes clusters. Before proceeding, follow the installation documentation that corresponds to your platform. This guide will be using version 1.24.

  • helm - Package manager used for installing and managing Kubernetes applications. In this guide, you will be using a Helm chart to install Tabnine on our Kubernetes cluster. For more information, see Installing Helm. This guide will be using version 3.12.0 ( 3.12.0 is our minimal supported version).

  • An available Kubernetes cluster. If you need to set up a cluster, we have provided the below installation guide for a self-hosted server. It provides step-by-step instructions intended to get you up and running as fast as possible. Guide applies for a self-hosted solution on your VPC as well as setting up a physical appliance inside your organizational network.

Deploy Tabnine

This guide assumes you have internet access to Tabnine docker and Helm charts registries for installation and updates (registry.tabnine.com / 34.72.243.185). If that is not the case, please follow this guide instead.

Set up namespaces

kubectl create ns tabnine
kubectl label namespaces tabnine name=tabnine --overwrite=true

Pull secrets

Instead of setting up a pull secret on isolated environments, you will need to make the docker images available in your environment; follow this guide.

kubectl create secret docker-registry regcred -n tabnine --docker-server=registry.tabnine.com --docker-username="IMAGES_USER" --docker-password="IMAGES_PASSWORD"

Import the SSL Certificate

For this step, we assume the certificate files are server.key and server.crt and that they are available in the same path as the console. We also assume that Tabnine will be installed at the tabnine namespace.

kubectl create secret --namespace tabnine tls tabnine-enterprise-app-cert --cert=./server.crt --key=./server.key

Install Tabnine

  1. Before you install, configure the values.yaml file contents used by the Helm Chart. The majority of the values for this chart have defaults recommended by Tabnine but you will want to review and modify the configuration to meet your specific requirements. This guide covers configuration values which must be updated to deploy Tabnine. You should review the entire configuration to understand all the possible options. Use the following values.yamlas a starting point to your configuration:

global:
  image:
    # imagePullSecrets -- The name of the secret contains the credentials for Tabnine registry
    imagePullSecrets:
      - name: regcred
  ingress:
    # host -- tabnine cluster domain, e.g. `tabnine.company.com`
    host: null
    tls:
      # hosts -- tabnine cluster domain, e.g. `tabnine.company.com`
      - hosts:
          []
          # - tabnine.company.com
        # secretName -- The secret name holds the SSL certificate
        secretName: tabnine-enterprise-app-cert
  
  tabnine:
    #  organizationId/Name/Secret -- Provided by Tabnine with license file
    organizationId: null
    organizationName: null
    organizationSecret: null
    organizationDomain: null

    # License key - Provided by Tabnine with license file. Just copy and paste here before deployment.
    licenseKey: null

auth:
  # defaultEmail -- The first admin user email that will be created
  defaultEmail: null
  noEmailVerificationEnforced: true
  
  1. Now that values.yaml is updated, it is time to install the chart on the cluster

helm upgrade --install -n tabnine --create-namespace tabnine \
oci://registry.tabnine.com/self-hosted/tabnine-cloud --values values.yaml

Last updated

Was this helpful?