The module lifecycle stage: General Availability

Deckhouse Kubernetes Platform components interact with DVP resources through the DVP API. To configure this connection, create a new user (ServiceAccount), assign the necessary permissions, and generate a kubeconfig.

The provider supports working with only one disk in the virtual machine template. Make sure the template contains only one disk.

If the update-hostname module of the cloud-init package is not disabled, it is recommended to change its run frequency from always to once-per-instance.

To do this, modify the update-hostname module configuration in the /etc/cloud/cloud.cfg file:

cloud_init_modules:
  ...
  - [update-hostname, once-per-instance]
  ...

The update-hostname module can also be disabled completely by removing it from the cloud_init_modules module list in the /etc/cloud/cloud.cfg file.

Creating a user

Create a new user in the DVP cluster using the following command:

d8 k create -f -<<EOF
apiVersion: v1
kind: ServiceAccount
metadata:
  name: sa-demo
  namespace: default
---
apiVersion: v1
kind: Secret
metadata:
  name: sa-demo-token
  namespace: default
  annotations:
    kubernetes.io/service-account.name: sa-demo
type: kubernetes.io/service-account-token
EOF

Adding a role

Add a role to the created user in the DVP cluster using the following command:

d8 k create -f -<<EOF
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: sa-demo-rb
  namespace: default
subjects:
  - kind: ServiceAccount
    name: sa-demo
    namespace: default
roleRef:
  kind: ClusterRole
  name: d8:use:role:manager
  apiGroup: rbac.authorization.k8s.io
EOF

Generating a kubeconfig

Generate a kubeconfig to be used in the cluster initial configuration file:

cat <<EOF > kubeconfig
apiVersion: v1
clusters:
- cluster:
    server: https://<KUBE-APISERVER-URL>   # Replace this with the actual API server address for the cluster.
  name: <CLUSTER-NAME>                     # Replace with the cluster name.
contexts:
- context:
    cluster: <CLUSTER-NAME>                # Replace with the cluster name.
    user: sa-demo
    namespace: default
  name: sa-demo-context
current-context: sa-demo-context
kind: Config
preferences: {}
users:
- name: sa-demo
  user:
    token: $(d8 k get secret sa-demo-token -n default -o json | jq -rc .data.token | base64 -d)
EOF

Encode the generated kubeconfig file using Base64 encoding (it appears in the initial configuration file as follows):

base64 kubeconfig | tr -d '\n'