MetaKube Environment Setup

Step Goals

At the end of this part you will be able to

  • Setup a MetaKube Cluster,
  • Prepare all necessary Resources for Authentication purposes on your CI/CD Pipeline.


As described in Landscape Overview for a functional workflow multiple components need to exist. The endpoint of a CI/CD pipeline is usually a runtime environment.
In case of MetaKube Accelerator the defined runtime is a Kubernetes Cluster.
The Tutorial focuses on relevant aspects of the upcoming CI/CD pipeline, which needs some configuration items from said Cluster. The Description of necessary tasks to setup a proper Kubernetes Cluster are linked at the appropriate places.

Kubernetes Cluster Setup

For Setting up a Cluster, please refer to MetaKube - Create a Cluster. In order to deploy some of the Building Blocks, there is a minimum requirement of at least a flavor of m1c.medium for your nodes.
We assume that you create a separate cluster for each environment you choose to use.
Please make sure to either enable Horizontal Node Autoscaling or add enough worker nodes to satisfy your applications' needs.

Kubernetes Authentication for your CI/CD Pipeline (kubeconfig)

For Authentication purposes you can either use the role based Access Control(RBAC) or an external authentication Provider via OAuth2.

Role based Access Control

For RBAC-Permissions you can use your already defined kubeconfig or create an adjusted kubeconfig suiting your needs.
Save the kubeconfig and encrypt it with base64

#for linux OS
cat ~/.kube/kubeconfig | base64 -w0 > pipeline_kubeconfig