diff --git a/docs/docs/getting-started/index.html b/docs/docs/getting-started/index.html index b5bfd051..daa689ba 100644 --- a/docs/docs/getting-started/index.html +++ b/docs/docs/getting-started/index.html @@ -802,7 +802,7 @@
Prepare your Kubernetes cluster and set up your kubectl access.
Once you have a running Kubernetes cluster you can focus on installing Jenkins Operator according to the Installation guide.
+Once you have a running Kubernetes cluster you can focus on installing Jenkins Operator according to the Installation guide.
Listed below are the two ways to deploy Jenkins Operator. For details on how to customize your Jenkins instance, refer to Getting Started
-Install Jenkins Custom Resource Definition:
+First, install Jenkins Custom Resource Definition:
kubectl apply -f https://raw.githubusercontent.com/jenkinsci/kubernetes-operator/master/config/crd/bases/jenkins.io_jenkins.yaml There are two ways to deploy the Jenkins Operator.
- -Apply Service Account and RBAC roles:
+Then, apply the operator and other required resources:
kubectl apply -f https://raw.githubusercontent.com/jenkinsci/kubernetes-operator/master/deploy/all-in-one-v1alpha2.yamlWatch Jenkins Operator instance being created:
kubectl get pods -wNow Jenkins Operator should be up and running in the default namespace.
Now Jenkins Operator should be up and running in the default namespace.
+For deploying Jenkins, refer to Deploy Jenkins section.
There is an option to use Helm to install the operator. It requires the Helm 3+ for deployment.
+Alternatively, you can also use Helm to install the Operator (and optionally, by default, Jenkins). It requires the Helm 3+ for deployment.
Create a namespace for the operator:
$ kubectl create namespace <your-namespace>