You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+13-16
Original file line number
Diff line number
Diff line change
@@ -34,10 +34,7 @@ It is not required to run the Jenkins controller inside Kubernetes.
34
34
## Configuration
35
35
36
36
Fill in the Kubernetes plugin configuration.
37
-
In order to do that, you will open the Jenkins UI and navigate to
38
-
**Manage Jenkins -> Manage Nodes and Clouds -> Configure Clouds -> Add a new cloud -> Kubernetes** and enter
39
-
the *Kubernetes URL* and *Jenkins URL* appropriately, unless Jenkins is running in Kubernetes in which case
40
-
the defaults work.
37
+
In order to do that, you will open the Jenkins UI and navigate to **Manage Jenkins -> Manage Nodes and Clouds -> Configure Clouds -> Add a new cloud -> Kubernetes** and enter the *Kubernetes URL* and *Jenkins URL* appropriately, unless Jenkins is running in Kubernetes in which case the defaults work.
41
38
42
39
Supported credentials include:
43
40
@@ -95,7 +92,7 @@ Jenkins agent.
95
92
It should be noted that the main reason to use the global pod template definition is to migrate a huge corpus of
96
93
existing projects (including freestyle) to run on Kubernetes without changing job definitions.
97
94
New users setting up new Kubernetes builds should use the `podTemplate` step as shown in the example snippets
0 commit comments