rtyler
/
brokenco.de
1
0
Fork 0
Code Pull Requests Releases Activity

Update 2019-09-23-jenkins-kuberenetes-master-separation.md 

Minor typos
This commit is contained in:
Ken Rachynski 2019-09-24 08:54:37 -06:00 committed by GitHub
parent 4ddb42ee83
commit e07d4549b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_posts/2019-09-23-jenkins-kuberenetes-master-separation.md
View File

@ -44,7 +44,7 @@ a different set of access grants for Vault, different monitoring, alerting, and
auditing, is configured to run the Jenkins master among a number of other
important internal tools. A second cluster, which is trusted with far less
responsibility than the control plane is made available to the Jenkins
[Kuberntes plugin](https://github.com/jenkinsci/kubernetes-plugin).
[Kubernetes plugin](https://github.com/jenkinsci/kubernetes-plugin).
### Configuring Jenkins
@ -55,7 +55,7 @@ away first:
* The master requires a fixed JNLP port, e.g. 50000, which can be exposed
outside the control plane for agents to properly phone home.
* The [service account](https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/kubernetes/service-account.yml)
configuration recommended by the Kubernetes pluginneeds to be applied to the
configuration recommended by the Kubernetes plugin needs to be applied to the
untrusted Kubernetes cluster.
* Ensure the Jenkins master has HTTP and JNLP properly exposed.
* Network connectivity must allow the control plane to access the API