Skip to content

Router authn/z part 2.5: podcertcontroller: Don't load pod in podidentity signer - #2389

Merged
Lior Lieberman (LiorLieberman) merged 1 commit into
agent-substrate:mainfrom
ahmedtd:router-authnz-2.5
Oct 15, 2026
Merged

Lior Lieberman (LiorLieberman) merged 1 commit into
agent-substrate:mainfrom
ahmedtd:router-authnz-2.5

Conversation

@ahmedtd

Copy link
Copy Markdown
Collaborator

We should rely on the checks enforced by kube-apiserver. We don't need to double-check whether the pod exists.

Upcoming e2e test changes will rely on the fact that non-Kubelet clients are allowed to create arbitary PodCertificateRequests, even if the pod or service account they reference does not exist. This will allow the test code running in Github Actions (or on the developer's machine) to authenticate to the router running within the cluster.

@ahmedtd Taahir Ahmed (ahmedtd) changed the title Router authn/z 2.5: podcertcontroller: Don't load pod in podidentity signer Router authn/z part 2.5: podcertcontroller: Don't load pod in podidentity signer Oct 9, 2026
@EItanya

Eitan Yarmush (EItanya) commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator

Taahir Ahmed (@ahmedtd), is seems like the core function of this PR is actually the downstream mTLS changes to ingress. Can we update the description/purpose accordingly?

Edit: I see this is stacked?

@ahmedtd

Copy link
Copy Markdown
Collaborator Author

Taahir Ahmed (Taahir Ahmed (@ahmedtd)), is seems like the core function of this PR is actually the downstream mTLS changes to ingress. Can we update the description/purpose accordingly?

Edit: I see this is stacked?

Yes, this is stacked. I switched it to draft mode to make it clearer

@ahmedtd
Taahir Ahmed (ahmedtd) marked this pull request as ready for review October 13, 2026 23:38
@ahmedtd

Copy link
Copy Markdown
Collaborator Author

OK, this is now unstacked and ready for review.

We should rely on the checks enforced by kube-apiserver.  We don't need
to double-check whether the pod exists.

Upcoming e2e test changes will rely on the fact that non-Kubelet
clients are allowed to create arbitary PodCertificateRequests, even if
the pod or service account they reference does not exist.
Merged via the queue into agent-substrate:main with commit b83d607 Oct 15, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/network area/security Security related issue/pr area/tests Enhancing / fixing test coverage. kind/feature An enhancement / feature request or implementation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants