Non-prod environments¶
The ITsynch Suite is deployed to non production environments for testing/demos/etc. The environments are deployed in Azure Kubernetes Services. These are the instructions to connect in case you are assigned a task that requires so. Usually, dev's won't need to connect to the cluster directly.
- Connect to ITsynch VPN
- Inside activated container
az login
- Configure kubectl for azure:
az aks get-credentials --resource-group itsynch-suite-aks --name itsynch-aks --subscription itsynch-suite
- you must be connected to vpn. If you connect to VPN after running the container, exit and activate again. (you'll get error code -3 when running this step)
kubectl cluster-info
Ensure you are running against AKS by checking the URLs.kubectl get namespace
you should see there the non prod environments.
To deploy any environment simply use suite-apply
as usual, including for the
data-seeder
. The infrastructure usually won't need to be updated.
Cluster Deployment Notes¶
These are some notes that were taken when the cluster was deployed.
Bash | |
---|---|
- Subnets needs to be created for nodes, system pods and user pods.
- Private DNS Zone needs to be set up for
privatelink.eastus.azmk8s.io
1.If it's not in the same RG, aks identity needs to have read/write rbac- Needs to be linked to aks vnet
- Needs to be linked to hub
- Can be shared between multiple clusters
- For ssl to be loaded from keyvault, the CSI secret thingy identity needs to
have policy
az aks show --resource-group itsynch-suite-aks \ --name itsynch-aks \ --subscription itsynch-suite \ --query addonProfiles.azureKeyvaultSecretsProvider.identity.clientId \ --output tsv