Skip to content

ROX-35059: pass shared master and worker service accounts#80767

Draft
stehessel wants to merge 1 commit into
openshift:mainfrom
stehessel:ROX-35059/shared-master-and-worker-service-accounts
Draft

ROX-35059: pass shared master and worker service accounts#80767
stehessel wants to merge 1 commit into
openshift:mainfrom
stehessel:ROX-35059/shared-master-and-worker-service-accounts

Conversation

@stehessel

@stehessel stehessel commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

See https://github.com/stackrox/automation-flavors/pull/347 for context.

Summary by CodeRabbit

This PR modifies the OpenShift CI workflow configuration for the StackRox automation-flavors E2E testing pipelines, specifically adding support for shared master and worker service accounts.

Changes made:

Two workflow YAML files in the StackRox automation-flavors CI configuration have been updated to introduce two new environment variables:

  • MASTER_NODE_SERVICE_ACCOUNT: Points to the master node service account
  • WORKER_NODE_SERVICE_ACCOUNT: Points to the worker node service account

These variables are added to:

  1. The ocp-4-crun-e2e workflow (crun runtime variant) - as defaults in the ocp-4-create step
  2. The ocp-4-e2e workflow (standard variant) - as environment variables in the pre.env configuration

Practical impact:

These configuration changes allow the E2E test workflows to use dedicated service accounts for master and worker nodes, enabling more flexible and controlled test execution across different cluster node types. This supports the shared service account pattern referenced in the related automation-flavors repository changes.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 18, 2026
@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot

openshift-ci-robot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

@stehessel: This pull request references ROX-35059 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 bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

See https://github.com/stackrox/automation-flavors/pull/347 for context.

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 openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 18, 2026
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: ff98ec00-a5f7-4dd3-b23d-a1cc174e1c9c

📥 Commits

Reviewing files that changed from the base of the PR and between 1aa7b55 and 9181481.

📒 Files selected for processing (2)
  • ci-operator/step-registry/stackrox/automation-flavors/ocp-4-crun-e2e/stackrox-automation-flavors-ocp-4-crun-e2e-workflow.yaml
  • ci-operator/step-registry/stackrox/automation-flavors/ocp-4-e2e/stackrox-automation-flavors-ocp-4-e2e-workflow.yaml

Walkthrough

Two CI workflow YAML files for StackRox OCP 4 end-to-end tests each receive two new environment variable entries—MASTER_NODE_SERVICE_ACCOUNT and WORKER_NODE_SERVICE_ACCOUNT—with default service account values added to their ocp-4-create/pre step env sections.

Changes

OCP 4 Workflow Node Service Account Env Vars

Layer / File(s) Summary
Add node service account env vars
ci-operator/step-registry/stackrox/automation-flavors/ocp-4-crun-e2e/stackrox-automation-flavors-ocp-4-crun-e2e-workflow.yaml, ci-operator/step-registry/stackrox/automation-flavors/ocp-4-e2e/stackrox-automation-flavors-ocp-4-e2e-workflow.yaml
Both workflow files add MASTER_NODE_SERVICE_ACCOUNT and WORKER_NODE_SERVICE_ACCOUNT env defaults to their respective ocp-4-create/pre step env sections.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error)

Check name Status Explanation Resolution
No-Sensitive-Data-In-Logs ❌ Error PR adds service account email identifiers (openshift-master-node@acs-san-stackroxci.iam.gserviceaccount.com, openshift-worker-node@acs-san-stackroxci.iam.gserviceaccount.com) as environment variabl... Consider using secrets/credentials mechanism instead of default environment variables for service account identifiers, or ensure they are marked as non-loggable in CI configuration.
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'ROX-35059: pass shared master and worker service accounts' directly describes the main change—adding master and worker service account environment variables across two workflow files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR modifies only YAML workflow configuration files, not Ginkgo test code. The check for stable test names is not applicable to non-test files.
Test Structure And Quality ✅ Passed PR contains only YAML workflow configuration changes, no Ginkgo test code. The custom check for test structure and quality is not applicable to this PR.
Microshift Test Compatibility ✅ Passed PR adds no new Ginkgo e2e tests or test code; it only modifies CI workflow YAML configuration files by adding environment variables. The MicroShift compatibility check applies only when new tests a...
Single Node Openshift (Sno) Test Compatibility ✅ Passed No new Ginkgo e2e tests are added in this PR. The changes are limited to CI workflow YAML configuration files that add environment variables to existing workflow steps. The custom check applies onl...
Topology-Aware Scheduling Compatibility ✅ Passed Changes are to OpenShift CI workflow definitions, not deployment manifests, operator code, or controllers. No Kubernetes scheduling constraints (affinity, nodeSelector, topology spread, PDBs) are i...
Ote Binary Stdout Contract ✅ Passed PR modifies only YAML workflow configuration files adding environment variables; contains no executable code subject to stdout contract checks.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only modifies workflow YAML configuration files, not Ginkgo e2e test code. Check applies only to new test files with Ginkgo syntax (It(), Describe(), etc.).
No-Weak-Crypto ✅ Passed PR only adds CI/CD configuration with service account environment variables; contains no weak cryptographic algorithms, custom crypto implementations, or unsafe secret comparisons.
Container-Privileges ✅ Passed PR only modifies OpenShift CI workflow files (environment variables for service accounts). No container specifications, privileged settings, or security context configurations are present in the mo...
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stehessel

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 18, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@stehessel: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-stackrox-stackrox-master-ocp-4-22-qa-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-22-scanner-v4-install-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-22-operator-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-22-ui-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-22-fips-qa-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-22-compliance-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-22-nongroovy-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-22-vm-scanning-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-next-candidate-qa-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-next-candidate-scanner-v4-install-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-next-candidate-operator-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-next-candidate-ui-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-next-candidate-fips-qa-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-next-candidate-compliance-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-next-candidate-nongroovy-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-dev-preview-qa-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-dev-preview-scanner-v4-install-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-dev-preview-operator-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-dev-preview-ui-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-dev-preview-fips-qa-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-dev-preview-compliance-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-dev-preview-nongroovy-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-12-qa-e2e-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-12-scanner-v4-install-tests stackrox/stackrox presubmit Registry content changed
pull-ci-stackrox-stackrox-master-ocp-4-12-operator-e2e-tests stackrox/stackrox presubmit Registry content changed

A total of 164 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants