BCDevOps / OpenShift4-Migration

Scripts and info for Ministry teams migration from OpenShift 3.11 to 4.x
Apache License 2.0
3 stars 0 forks source link

Documentation on Artifactory and S2I #65

Closed jeremy-vernon-bcgov closed 2 years ago

jeremy-vernon-bcgov commented 3 years ago

Hello,

As per this thread: https://chat.pathfinder.gov.bc.ca/channel/devops-how-to?msg=Lnf9Hb2dDKa36XTed and this thread: https://chat.pathfinder.gov.bc.ca/channel/devops-artifactory?msg=mzGB3gJhw9RkkYPNR

To get Artifactory to work I followed the tutorial but did have the following stumbling blocks:

1) I think since we're an older tenant the name for our artifactory service account secret didn't match the format indicated in the tutorial (which is the newer, more legible, construction). I eventually saw the thread where that change was explained which got me past the first paragraph...until.

2) When using the S2I build strategy on my -test namespace after following the tutorial, builds would fail at the "pull builder image" step - with an error indicating that authentication failed. This is because I had linked the pull secret to the builder user in the -tools namespace but not the *-test namespace. oc project b07dd3-test -> oc secrets link default <secret-name> & oc secrets link builder <secret-name> ... resolved the issue.