At the end of this part you will be able to:
We describe in the Building Block Landscape Overview how a functional workflow and multiple components need to be provisioned.
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 the cluster.
(See further description of essential tasks to set up a Kubernetes Cluster appropriately from the description of the dedicated section.
The description of the tasks required to set up a proper Kubernetes cluster is linked in the appropriate places
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 m1c.medium flavor for your nodes.
We assume that you create a separate cluster for each environment (you choose what to use).
Please make sure to either enable Horizontal Node Autoscaling or add enough worker nodes to satisfy your application's requirements.
For Authentication purposes, you can either use the role based Access Control(RBAC) or an external authentication Provider via OAuth2.
#for linux OS kubeconfig -> may vary as the name of the file matches your cluster name cat ~/.kube/kubeconfig | base64 -w0 > pipeline_kubeconfig #for macos / if you download the kubeconfig from your sysEleven Dashboard the file # cat <yourDownloadPathOfKubeConfig> | base64 > pipeline_kubeconfig