Getting Started
Prerequisites
If you are reading this page, we assume that you already have asked for a cluster creation using Thales postit portal.
Install the following packages
- MacOS
- Linux
- Windows
brew update && brew install azure-cli
brew install kubectl
brew install Azure/kubelogin/kubelogin
sudo apt-get update
# install azure-cli
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
# install kubectl
sudo apt-get install -y apt-transport-https ca-certificates curl
sudo curl -fsSLo /usr/share/keyrings/kubernetes-archive-keyring.gpg https://packages.cloud.google.com/apt/doc/apt-key.gpg
echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list<br/>
sudo apt-get update
sudo apt-get install -y kubectl
# Open a powershell
choco install kubernetes-cli
$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
Access to the cluster
After the cluster creation, you receive by email:
- K8SAAS_TENANT_ID: the tenant it
- K8SAAS_SUBSCRIPTION_ID: the id of the subscription where your resources are deployed
- K8SAAS_RESOURCE_NAME: the name of the kubernetes and the resource group
Keep these variables in a file:
touch set_k8saas_env_variables.sh
chmod u+x set_k8saas_env_variables.sh
Update YOUR_K8SAAS_TENANT_ID with the YOUR_K8SAAS_TENANT_ID value received by email:
echo "export K8SAAS_TENANT_ID=YOUR_K8SAAS_TENANT_ID" >> set_k8saas_env_variables.sh
Update K8SAAS_SUBSCRIPTION_ID with the YOUR_K8SAAS_SUBSCRIPTION_ID value received by email:
echo "export K8SAAS_SUBSCRIPTION_ID=YOUR_K8SAAS_SUBSCRIPTION_ID" >> set_k8saas_env_variables.sh
Update K8SAAS_RESOURCE_NAME with the YOUR_K8SAAS_RESOURCE_NAME value received by email:
echo "export K8SAAS_RESOURCE_NAME=YOUR_K8SAAS_RESOURCE_NAME" >> set_k8saas_env_variables.sh
Once, done, follow the following steps to get your nominative kubeconfig:
source set_k8saas_env_variables.sh
az login -t "$K8SAAS_TENANT_ID"
az aks get-credentials \
--name "$K8SAAS_RESOURCE_NAME" \
--resource-group "$K8SAAS_RESOURCE_NAME" \
--subscription "$K8SAAS_SUBSCRIPTION_ID"
kubelogin convert-kubeconfig -l azurecli
That's all !!! You should be able to access to your k8saas cluster
First steps & Configuration Check
- Kubectl context
- Get pods
Verify your kubectl context:
kubectl config get-contexts
You should see at least a line with your k8saas cluster, like:
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
* k8saas-lja-273-sandbox k8saas-lja-273-sandbox clusterUser_k8saas-lja-273-sandbox_k8saas-lja-273-sandbox
kubectl get pods --namespace dev
You should see:
No resources found in dev namespace.
Next steps & Start using k8saas
Who are you ?
- I'm new with Kubernetes
- I'm a cloud expert
- I'm a devops
- I'm a developer
Welcome in the kubernetes world ! To begin, we recommend to follow the simple tutorial, where you learn how to deploy a simple container from internet, and how to make it accessible from anyone.
K8SAAS runs in a dedicated environment, but it's recommended to combine it with a IaaS Landing Zone. Then, you will have all the following possibilities:
- Combine k8saas with an azure bastion
- Combine k8saas with a managed database
And Discover all our integrations
K8SAAS provides several services to facilitate deployment from a ci/cd pipeline using a generic kubeconfig. Learn how to Get the kubeconfig of a service account.
Observability stack is by default deployed to bring your visibility using:
And Discover all our features and Tutorials to for instance improve your helm charts, and optimize your resources
We have build
The community around k8saas is growing, have a look at the Community Section to discover how other product uses us.
A Tutorial section is available [here] to help you building Dockerfiles and use kubernetes efficiently