Fix e2e-aws metrics-test PodSecurity violations and flake cascade - #1006
Fix e2e-aws metrics-test PodSecurity violations and flake cascade#1006vickeybrown wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vickeybrown The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
70dac7a to
f287023
Compare
f287023 to
96fb498
Compare
|
/test e2e-aws |
85b23dd to
0cfec4f
Compare
|
@vickeybrown: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
0cfec4f to
e3d6238
Compare
Summary
Supersedes #1005 — includes all of @parametalol's changes plus one additional fix:
runOCandGetOutput— ephemeral metrics pods routinely hit curl exit 7 (connection refused) while the metrics service is coming up; retries withwait.PollImmediateinstead of failing on the first attempt (from Fix e2e-aws flake cascade and metrics-pod connection race #1005)InitializeClusterResourcesnow deletes and recreates cluster-scoped RBAC objects left behind by a previous test whose cleanup was skipped, instead of hard-failing on "already exists" (from Fix e2e-aws flake cascade and metrics-pod connection race #1005)restricted:latestsecurity context tometrics-testpods — all fouroc runcall sites now include--overridessettingrunAsNonRoot,seccompProfile,allowPrivilegeEscalation=false, andcapabilities.drop=["ALL"]so the ephemeral pods comply with enforced PodSecurity policyTest plan
go build ./tests/...go vet ./tests/...e2e-awsProw job passesCo-Authored-By: Michaël github@parameta.lol
🤖 Generated with Claude Code