mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[GH-ISSUE #527] [feature] kubectl command #135
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#135
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ElGigi on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/527
Wouldn't it be interesting to integrate the same mechanics as for the ssh command with the kubectl command?
That we can share tokens between users/groups to access Kubernetes contexts?
This would allow to control access to clusters through the bastion and benefit from all the advantages of security and access controls.
If we went further, to have an ephemeral disk space to write yaml files for example. Ephemeral disk space that would be deleted when the session disconnects or regularly.
Also have access to the helm command can be which interacts with the kubectl command.