Bug: add a task of automatically linking the secret to sa during the pipeline run

[tkulik]

In order to use a private registry, the registry secret must be linked to the service account that will deploy the application.

oc -n kabanero secrets link <service-account> my-registry --for=pull,mount

However, today the pipeline doesn't automatically do this so the resulting pod fails with ImagePullBackOff errors until Todd manually find the correct SA, applies the link, and deletes the pod.

To Reproduce
Steps to reproduce the behavior:

1. Follow these instructions for private registry:
   https://www.ibm.com/support/knowledgecenter/SSCSJL_4.1.x/settingup.html
2. Then deploy some app using these newly created stacks using appsody.
3. Result: the pod is in ImagePullBackOff state.
4. To fix this problem:
   1. find the Service Account for the application by looking in the pod yaml,
   2. run this cmd:
      oc -n kabanero secrets link <service-account> my-registry --for=pull,mount
   3. Delete the pod and it will get regenerated.

After this the application works. We need a better solution, this seems just a workaroud. Perhaps we can automatically link the secret to serviceAccount during the pipeline run.

[marikaj123]

Hi @kvijai82 - Please help to find the appropriate owner and assign a release to the this issue. Thank you.