Kubectl Access

Mission Control SaaS instances are deployed on dedicated vCluster instances.

Mission Control configuration is managed through Kubernetes Custom Resource Definitions (CRDs). Depending on your deployment model, you may need to apply resources directly to the vCluster. To facilitate this, you can download a kubeconfig file after authentication.

The access token provided has role-based permissions limited to either mission-control-reader or mission-control-writer, based on your selected role. Use this kubeconfig file to interact with your Mission Control SaaS instance via kubectl.

Production

For production environments, it is recommended to use GitOps tools like Argo CD or Flux to manage configurations rather than applying them directly with kubectl. Use the kubeconfig file to configure your GitOps tool to target the Mission Control SaaS instance.

1. Save the kubeconfig to your GitOps cluster:

   kubectl create secret generic mission-control-kubeconfig \
     -n flux-system \
     --from-file=KUBECONFIG=./kubeconfig
   

2. Reference the kubeconfig when deploying Mission Control manifests:

   apiVersion: kustomize.toolkit.fluxcd.io/v1
   kind: Kustomization
   metadata:
     name: mission-control-config
     namespace: flux-system
   spec:
     interval: 10m
     path: ./
     prune: true
     sourceRef:
       kind: GitRepository
       name: mission-control-gitops
     kubeConfig:
       secretRef:
         name: mission-control-kubeconfig
         key: KUBECONFIG