How to deploy Calyptia Core on top of Kubernetes Clusters
Overview
Calyptia Core deploys as an application within your existing Kubernetes cluster with support for OnPrem, Public Cloud Distributions, and Enterprise variants.
Supported Versions
Distribution
Minimum Version
Open Source Kubernetes
1.19+
Amazon Kubernetes Service (EKS)
1.19+
Azure Kubernetes Service (AKS)
1.19+
Google Kubernetes Engine (GKE)
1.19+
Red Hat Open Shift
4.0
Calyptia Core Console
When visiting the Calyptia Core homepage for the first time click on New Instance and fill out a Name and Tags.
After filling out the properties, all commands for Calyptia CLI, Helm, and Kubectl are shown for onboarding.
Calyptia CLI
One of the easiest ways to install on top of Kubernetes is to use the calyptia cli. The Calyptia CLI allows you to manage, operate, and create multiple core instances. Before getting started, you need to ensure the following two requirements are fulfilled
Check that the current Kubernetes context is configured to the cluster you wish to deploy in. You can run kubectl get nodes to check which cluster is in the current context
You need the proper token for authentication. This can be retrieved from the Calyptia Core home page > Create Core Instance > Calyptia CLI after filling out the name and tags you wish to use
Deployment
While you can use the pre-populated calyptia cli command for deploying you may want to adjust particular settings which can be done by running the following command.
Using the create command, the Calyptia CLI uses your local Kubernetes configuration file.
calyptia create core_instance kubernetes
Video of create via Calyptia CLI
Additional Calyptia CLI create options
Setup a new core instance on Kubernetes
Usage:
calyptia create core_instance kubernetes [flags]
Aliases:
kubernetes, kube, k8s
Flags:
--environment string Calyptia environment name or ID
-h, --help help for kubernetes
--kube-as string Username to impersonate for the operation
--kube-as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
--kube-as-uid string UID to impersonate for the operation
--kube-certificate-authority string Path to a cert file for the certificate authority
--kube-client-certificate string Path to a client certificate file for TLS
--kube-client-key string Path to a client key file for TLS
--kube-cluster string The name of the kubeconfig cluster to use
--kube-context string The name of the kubeconfig context to use
--kube-insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
-n, --kube-namespace string If present, the namespace scope for this CLI request
--kube-password string Password for basic authentication to the API server
--kube-proxy-url string If provided, this URL will be used to connect via proxy
--kube-request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
--kube-server string The address and port of the Kubernetes API server
--kube-tls-server-name string If provided, this name will be used to validate server certificate. If this is not provided, hostname used to contact the server is used.
--kube-token string Bearer token for authentication to the API server
--kube-user string The name of the kubeconfig user to use
--kube-username string Username for basic authentication to the API server
--name string Core instance name (autogenerated if empty)
--no-healthcheck-pipeline Disable health check pipeline creation alongside the core instance
--tags strings Tags to apply to the core instance
--version string Core instance version (latest is the default)
kubectl
When using kubectl you can use the all-in-one script generated from the User Interface. The template script can be found here
Helm
Helm as a packaging manager for Calyptia is an effective way to manage Calyptia Core as a deployment and is preferred for many that are already managing other deployments via Helm
Adding Calyptia Helm Repo
helm repo add calyptia http://helm.calyptia.com
Updating Calyptia Helm Repo
helm repo update
Deployment
When deploying Calyptia Core, we recommend specifying a custom namespace when deploying the control plane. In the command below the namespace, calyptia is being used.
helm install \
--namespace calyptia \
--create-namespace calyptia-core calyptia/core \
--set project_token=<TOKEN IN CALYPTIA CORE CONSOLE> \
--set name=<NAME FOR THE CORE INSTANCE>
