fix: Update controller-build-scc.yaml

[theodor2311]

Use security.openshift.io/v1 instead of v1 to fix no matches for kind "SecurityContextConstraints" in version "v1" for OpenShift.

[jenkins-x-bot]

Hi @theodor2311. Thanks for your PR.

I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign garethjevans
You can assign the PR to them by writing /assign @garethjevans in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[theodor2311]

/assign @garethjevans

[jenkins-x-bot]

@theodor2311: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[manuelwallrapp]

I changed this locally in my config repo jenkins-x-boot-config repo. After I changed it, I still get following error:
error: unable to recognize "/var/folders/6t/vc9qjw1x1yg1kvb_8k04m6cc0000gn/T/helm-template-workdir-230695889/jenkins-x/output/namespaces/jx/env/charts/jxboot-resources/templates/part0-scc-controllerbuild.yaml": no matches for kind "SecurityContextConstraints" in version "v1"'

Will this Yaml from somewhere else applied than the local repo?

[theodor2311]

I changed this locally in my config repo jenkins-x-boot-config repo. After I changed it, I still get following error:
error: unable to recognize "/var/folders/6t/vc9qjw1x1yg1kvb_8k04m6cc0000gn/T/helm-template-workdir-230695889/jenkins-x/output/namespaces/jx/env/charts/jxboot-resources/templates/part0-scc-controllerbuild.yaml": no matches for kind "SecurityContextConstraints" in version "v1"'

Will this Yaml from somewhere else applied than the local repo?

It will not work if you only modify this yaml file, I get around by skipping the install-jenkins-x pipeline step and manually applied the charts with modification. I just submitted a PR to the jenkins-x-charts, hope I hit the right file.
jenkins-x-charts/jxboot-resources#45

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale