CloudBees recommends using Kubernetes namespaces when you install CloudBees CI.
When combined with Kubernetes RBAC security, Kubernetes namespaces help a Kubernetes administrator restrict who has access to a namespace and its data.
To set up a Kubernetes namespace:
Type the following commands:
$ kubectl create namespace cloudbees-core $ kubectl config set-context $(kubectl config current-context) --namespace=cloudbees-core
The open-source tools |
The administrator should choose which computer will be used to install, update, and maintain CloudBees CI.
This administration workstation may be either the CloudBees CI administrative workstation or a Kubernetes administrative workstation. It must be a workstation on which you have full command privileges for the following utilities:
kubectlKubernetes Control client application. See Supported platforms for CloudBees CI on modern cloud platforms.
The Helm client. Follow the instructions in the Helm Quickstart Guide to install the Helm client.
If you intend to use the Helm |
CloudBees hosts the Helm chart on CloudBees' public Helm Chart Repository. Before you can use the
CloudBees repository you must add it to your Helm environment with the
helm repo add command.
To add the CloudBees Public Helm Chart Repository to your Helm environment:
$ helm repo add cloudbees https://charts.cloudbees.com/public/cloudbees (1) $ helm repo update (2)
Always run |
CloudBees CI requires an NGINX Ingress Controller.
You can skip this section if:
You already have an NGINX Ingress Controller installed. CloudBees CI can utilize an existing controller.
You plan to install a new NGINX Ingress Controller as part of installing the CloudBees CI Helm chart. Using the Helm chart from CloudBees guarantees that the NGINX Ingress Controller meets CloudBees CI’s requirements.
If you do not already have an NGINX Ingress Controller installed and you do not want to install it while you are installing CloudBees CI, follow the steps below.