WIP: CNTRLPLANE-1544: Enable user namespaces for the operator

[tchap]

The operator now uses hostUsers: false in the associated deployment.
All relevant user and group IDs are set to 1000.

[openshift-ci-robot]

@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.21.0" version, but no target version was set.

In response to this:

I am currently just researching user namespaces for future implementation, ignore this for now.

---

This goes for both the operator and the operand.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue.

In response to this:

The operator now uses hostUsers: false in the associated deployment.
All relevant UIDs are set to 1000.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue.

In response to this:

The operator now uses hostUsers: false in the associated deployment.
All relevant UIDs are set to 1000.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue.

In response to this:

The operator now uses hostUsers: false in the associated deployment.
All relevant user and group IDs are set to 1000.

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 openshift-eng/jira-lifecycle-plugin repository.

[tchap]

/retest

[ingvagabund]

error: couldn't retrieve test suites: failed to extract test binaries: encountered errors while extracting binaries: extracted binary at path "/tmp/home/.cache/openshift-tests/registry_build11_ci_openshift_org_ci-op-f7fcxfi0_release_sha256_0388b9ca7834da3335973fc3227c497b3dd1381d9d00bcfdb9a039546c7985ae_30911f771b1c/cluster-openshift-controller-manager-operator-tests-ext.gz" does not exist. the src path "/usr/bin/cluster-openshift-controller-manager-operator-tests-ext.gz" doesn't exist in image "registry.build11.ci.openshift.org/ci-op-f7fcxfi0/stable@sha256:1c8201686a31daa339fea1667d701a2b399c59e1ce5e6c94881d0a3e32c479ca". note the version of origin needs to match the version of the cluster under test

[tchap]

error: couldn't retrieve test suites: failed to extract test binaries: encountered errors while extracting binaries: extracted binary at path "/tmp/home/.cache/openshift-tests/registry_build11_ci_openshift_org_ci-op-f7fcxfi0_release_sha256_0388b9ca7834da3335973fc3227c497b3dd1381d9d00bcfdb9a039546c7985ae_30911f771b1c/cluster-openshift-controller-manager-operator-tests-ext.gz" does not exist. the src path "/usr/bin/cluster-openshift-controller-manager-operator-tests-ext.gz" doesn't exist in image "registry.build11.ci.openshift.org/ci-op-f7fcxfi0/stable@sha256:1c8201686a31daa339fea1667d701a2b399c59e1ce5e6c94881d0a3e32c479ca". note the version of origin needs to match the version of the cluster under test

I know, but I have no idea what that is about right now. Seems completely unrelated.

[ingvagabund]

/test ci/prow/okd-scos-e2e-aws-ovn

[openshift-ci]

@ingvagabund: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-aws-operator

/test e2e-aws-operator-preferred-host

/test e2e-aws-ovn

/test e2e-aws-ovn-upgrade

/test e2e-tests-extension

/test images

/test okd-scos-images

/test unit

/test verify

/test verify-deps

The following commands are available to trigger optional jobs:

/test okd-scos-e2e-aws-ovn

/test security

Use /test all to run all jobs.

In response to this:

/test ci/prow/okd-scos-e2e-aws-ovn

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 kubernetes-sigs/prow repository.

[ingvagabund]

/test okd-scos-e2e-aws-ovn

[ingvagabund]

/approve

[ingvagabund]

/lgtm

[tchap]

/retest

[ingvagabund]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, tchap

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ingvagabund]

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

[openshift-ci]

@tchap: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-upgrade	74354a6	link	true	/test e2e-aws-ovn-upgrade

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.