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
HACKING.md: Add note about RHCOS pipeline in ITUP clusters
Add a note about needing the the `shard=internal` label added to
the Jenkins route to run the RHCOS pipeline in the internal ITUP
clusters. It's also necessary to add the .int sub domain to the
jenkins URL, specifically `jenkins-<NAMESPACE>.apps.int.<cluster-URL>`.
Copy file name to clipboardExpand all lines: HACKING.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -609,6 +609,22 @@ password works to log in as `developer`.
609
609
It may be a good idea to set the Kubernetes plugin to
610
610
[use DNS for service names](TROUBLESHOOTING.md#issue-for-jenkins-dns-names).
611
611
612
+
#### [OPTIONAL] Add internal router shard label to Jenkins route
613
+
614
+
To run the RHCOS pipeline in the internal ITUP clusters, the Jenkins route must have the `shard=internal` label added to the route and the hostname URL must be updated to include `apps.int`.
615
+
616
+
Manually edit the route after pipeline deployment:
617
+
```
618
+
# optionally run this if the route already exists
619
+
oc delete route jenkins
620
+
621
+
# recreate the route with the right label and hostname
622
+
oc expose service jenkins -l shard=internal --hostname jenkins-<NAMESPACE>.apps.int.<cluster-URL>
623
+
624
+
# if label was not added, manually add it to the new route
625
+
oc label routes jenkins shard=internal
626
+
```
627
+
612
628
### Running the pipeline
613
629
614
630
Once Jenkins is ready, make sure that the seed job has been run successfully.
0 commit comments