Skip to content

Fix statusz port in k8s credential provider - #3067

Merged
Benjamin Elder (BenTheElder) merged 1 commit into
agent-substrate:mainfrom
yufan-su:credential-provider-statusz-loopback
Oct 23, 2026
Merged

Benjamin Elder (BenTheElder) merged 1 commit into
agent-substrate:mainfrom
yufan-su:credential-provider-statusz-loopback

Conversation

@yufan-su

Copy link
Copy Markdown
Collaborator

Fixes #3033

k8s-credential-provider served its unauthenticated /statusz page.

--status-address now defaults to 127.0.0.1:4040. The manifest passes the same value and no longer declares the statusz container port. To reach the page:

kubectl -n ate-system port-forward deploy/k8s-credential-provider 4040:4040

Checked on kind: the node and the provider's own pod network get connection refused on :4040, and port-forward still serves the page.

AI use: I used Claude Code to write the change and run the kind check, and reviewed the diff myself.

  • Tests pass
  • Docs updated

@BenTheElder
Benjamin Elder (BenTheElder) added this pull request to the merge queue Oct 23, 2026
Merged via the queue into agent-substrate:main with commit d035819 Oct 23, 2026
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Low] Bind k8s-credential-provider /statusz to 127.0.0.1:4040 by default

3 participants