Manual setup
Setup KuboVisor cloud manually.
π· Service account
We recommend to create a specific ServiceAccount object in your cluster to authenticate KuboVisor and grant it specific permissions, but nothing prevents you from using an already existing service account.
In this example, the service account ksa-kubovisor will be created in the kubovisor namespace. You are free to rename the service account and/or to create it in another namespace.
kubectl create namespace kubovisor
kubectl create serviceaccount ksa-kubovisor --namespace kubovisorkubectl version --short=trueapiVersion: v1
kind: Secret
metadata:
namespace: kubovisor
name: ksa-kubovisor
annotations:
kubernetes.io/service-account.name: ksa-kubovisor
type: kubernetes.io/service-account-tokenkubectl apply -f kubovisor-secret.yamlReferences:
βοΈ Permissions
We currently provide two different set of permissions:
****limited permissions that will allow us to dig deeper in our analysis of your cluster.
****read-only permissions that will enable a base set of features.
Limited write
This set of permissions grants us read-only access to all deployed resources on your cluster, in all namespaces, as well as read-write access to pods in kubovisor namespace. We wonβt be able to temper with resources outside of kubovisor namespace, only see them.
To define these permissions, we use the ClusterRole, ClusterRoleBinding, Role and RoleBinding objects and link them to the service account we created earlier.
This is the YAML definition of these objects:
You can create them by applying the YAML definition or with the following commands:
Read-only
This set of permissions grants us read-only access to all deployed resources on your cluster, in all namespaces. We wonβt be able to temper with them, only see them.
To define these permissions, we use the ClusterRole and ClusterRoleBinding objects and link them to the service account we created earlier.
This is the YAML definition of these objects:
You can create them by applying the YAML definition or with the following commands:
π Credentials generation
Last step is to generate a kubeconfig file for the ksa-kubovisor ServiceAccount that we created earlier. You can use our hand-crafted Bash script to quickly generate one:
At the end of the execution, a kubeconfig file will be generated in the current directory. Use this kubeconfig on KuboVisor to add your cluster.
Last updated