Repository navigation
Commit b515fce
committed
test(kubernetes): assert the tenant OIDC UID header on the control plane
The render matrix proves the chart emits
--requestheader-uid-headers, but nothing checked that the flag survives
the path a real tenant takes: aggregated API admission of spec.oidc, the
HelmRelease, and the rendered KamajiControlPlane. Assert it in both OIDC
end-to-end suites, next to the existing --authentication-config check on
the same resource.
Neither suite starts a Kamaji control plane, so this covers the object
the chart produces, not an apiserver booting with the flag. Both tenants
pin Kubernetes v1.35, where RemoteRequestHeaderUID is enabled by
default, so only the header flag is expected.
Assisted-By: Claude <[email protected]>
Signed-off-by: Aleksei Sviridkin <[email protected]>1 parent 42864c9 commit b515fce
2 files changed
Lines changed: 11 additions & 0 deletions
File tree
- hack/e2e-chainsaw
- kubernetes-oidc-customconfig
- kubernetes-oidc-system
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
64 | 69 | | |
65 | 70 | | |
66 | 71 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
73 | 73 | | |
74 | 74 | | |
75 | 75 | | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
76 | 82 | | |
77 | 83 | | |
78 | 84 | | |
| |||
0 commit comments