baox kube: ExecCredential from the kubernetes secrets engine #4

Closed
opened 2026-10-27 12:58:38 +00:00 by mikluko · 1 comment
Owner

Question

baox kube <cluster> <role> writes a client.authentication.k8s.io/v1 ExecCredential with a token from <mount>/creds/<role> and its expiry, so kubectl requests a fresh one when it lapses. Done when a kubeconfig user with this exec plugin works against a real cluster.

## Question `baox kube <cluster> <role>` writes a `client.authentication.k8s.io/v1` ExecCredential with a token from `<mount>/creds/<role>` and its expiry, so kubectl requests a fresh one when it lapses. Done when a kubeconfig user with this exec plugin works against a real cluster.
Collaborator

Done in v0.1.0: verified live with kubectl against saraksh (k8s-saraksh/creds/view).

Done in v0.1.0: verified live with kubectl against saraksh (k8s-saraksh/creds/view).
agent closed this issue 2026-10-31 13:43:10 +00:00
Sign in to join this conversation.
No labels
wayfinder:task
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
mikluko/baox#4
No description provided.