Skip to content

Set Up Kiosk⚓︎

Kiosk is a multi-tenancy extension for managing tenants and namespaces in a shared Kubernetes cluster. Within EDP, Kiosk is used to separate resources and enables the following options (see more details):

  • Access to the EDP tenants in a Kubernetes cluster;
  • Multi-tenancy access at the service account level for application deploy.

Inspect the main steps to set up Kiosk for the proceeding EDP installation.

Note

Kiosk deploy is mandatory for EDP v.2.8. In earlier versions, Kiosk is not implemented. Since EDP v.2.9.0, integration with Kiosk is an optional feature. You may not want to use it, so just skip those steps and disable in Helm parameters during EDP deploy.

# global.kioskEnabled: <true/false>

Prerequisites⚓︎

Note

This tool needs to be installed in advance before deploying EDP.

Installation⚓︎

  • Deploy Kiosk version 0.2.11 in the cluster. To install it, run the following command:
      # Install kiosk with helm v3

  helm repo add kiosk https://charts.devspace.sh/
  kubectl create namespace kiosk
  helm install kiosk --version 0.2.11 kiosk/kiosk -n kiosk --atomic

For more details, please refer to the Kiosk page on the GitHub.

Configuration⚓︎

To provide access to the EDP tenant, follow the steps below.

  • Check that a security namespace is created. If not, run the following command to create it:
      kubectl create namespace security

Note

On an OpenShift cluster, run the oc command instead of kubectl one.

  • Add a service account to the security namespace.
      kubectl -n security create sa edp

Info

Please note that edp is the name of the EDP tenant here and in all the following steps.

  • Apply the Account template to the cluster. Please check the sample below: 
    apiVersion: tenancy.kiosk.sh/v1alpha1
kind: Account
metadata:
  name: edp-admin
spec:
  space:
    clusterRole: kiosk-space-admin
  subjects:
  - kind: ServiceAccount
    name: edp
    namespace: security
  • Apply the ClusterRoleBinding to the 'kiosk-edit' cluster role (current role is added during installation of Kiosk). Please check the sample below: 
    apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: edp-kiosk-edit
subjects:
- kind: ServiceAccount
  name: edp
  namespace: security
roleRef:
  kind: ClusterRole
  name: kiosk-edit
  apiGroup: rbac.authorization.k8s.io
  • To provide access to the EDP tenant, generate kubeconfig with Service Account edp permission. The edp account created earlier is located in the security namespace.