Tobias Brunner
c4f7c8df69
All checks were successful
Build and Deploy Staging / build (push) Successful in 1m12s
Build and Deploy Antora Docs / build (push) Successful in 40s
Tests / test (push) Successful in 24s
Build and Deploy Staging / deploy (push) Successful in 10s
Build and Deploy Antora Docs / deploy (push) Successful in 5s
30 lines
No EOL
887 B
Text
30 lines
No EOL
887 B
Text
= Web Portal Control-Planes
|
|
|
|
Each control-plane represents a zone at a cloud provider. It's a dedicated Kubernetes API endpoint running the Servala control-plane.
|
|
|
|
To register a control-plane, a service account with appropriate permissions is required on the Kubernetes API server.
|
|
|
|
Example:
|
|
|
|
[source,bash]
|
|
----
|
|
# Create service account
|
|
kubectl -n kube-system create sa servala-portal
|
|
|
|
# Create long-lived token for service account
|
|
kubectl -n kube-system apply -f - <<EOF
|
|
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: servala-portal-token
|
|
annotations:
|
|
kubernetes.io/service-account.name: servala-portal
|
|
type: kubernetes.io/service-account-token
|
|
EOF
|
|
|
|
# Grant access
|
|
kubectl create clusterrolebinding servala-portal-admin --clusterrole=cluster-admin --serviceaccount=kube-system:servala-portal
|
|
|
|
# Retrieve token
|
|
kubectl ksd -n kube-system get secret servala-portal-token -o yaml
|
|
---- |