Remove Node viewing ClusterRole from E2E-on-OCP workflow#312
Closed
MikeSpreitzer wants to merge 1 commit intollm-d-incubation:mainfrom
Closed
Remove Node viewing ClusterRole from E2E-on-OCP workflow#312MikeSpreitzer wants to merge 1 commit intollm-d-incubation:mainfrom
MikeSpreitzer wants to merge 1 commit intollm-d-incubation:mainfrom
Conversation
Modify the GHA workflow that does E2E test in our shared OpenShift cluster so that it does not create, delete, nor use a ClusterRole for reading Nodes. Signed-off-by: Mike Spreitzer <[email protected]>
Collaborator
Author
|
Oops, wrong fork. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the OpenShift E2E GitHub Actions workflow to stop creating/deleting a dedicated ClusterRole for Node read access, and to stop passing that ClusterRole name into the Helm install.
Changes:
- Removed workflow steps that create/delete the
fma-node-viewerClusterRole. - Removed the Helm
--set global.nodeViewClusterRole=...override so the chart no longer creates the associated ClusterRoleBinding. - Removed cluster-scoped cleanup commands related to the node-view RBAC resources.
Comments suppressed due to low confidence (1)
.github/workflows/ci-e2e-openshift.yaml:498
- Removing the
global.nodeViewClusterRoleHelm value means the fma-controllers chart will no longer create the ClusterRoleBinding that grants the controller ServiceAccount get/list/watch on Nodes (see chart templates/rbac/role-binding.yaml conditional on that value). The dual-pods controller registers a Nodes informer/lister and uses it during reconciliation (e.g., itGet()s the Node and returns early when it is missing), so in a default install this will prevent launcher/providing Pods from being created and will likely break this workflow’s E2E assertions. If the goal is to avoid creating/deleting ClusterRoles in CI, consider instead binding to an existing, pre-provisioned ClusterRole that grants minimal Node read access, or update the controller/chart so Node access is not required for these E2E paths.
helm upgrade --install "$FMA_RELEASE_NAME" charts/fma-controllers \
-n "$FMA_NAMESPACE" \
--set global.imageRegistry="${CONTROLLER_IMAGE%/dual-pods-controller:*}" \
--set global.imageTag="${CONTROLLER_IMAGE##*:}" \
--set dualPodsController.sleeperLimit=2 \
--set global.local=false \
--set dualPodsController.debugAcceleratorMemory=false \
--set launcherPopulator.enabled=false
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Modify the GHA workflow that does E2E test in our shared OpenShift cluster so that it does not create, delete, nor use a ClusterRole for reading Nodes.
This is, at the moment, a test; not to be merged as is.