Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

operator: Do not store sensitive information directly in Operator CRDs #22557

Closed
Tracked by #29480
TeleLos opened this issue Mar 2, 2023 · 1 comment
Closed
Tracked by #29480

operator: Do not store sensitive information directly in Operator CRDs #22557

TeleLos opened this issue Mar 2, 2023 · 1 comment
Labels
c-aq Internal Customer Reference c-ca Internal Customer Reference c-gy Internal Customer Reference c-vo Internal Customer Reference feature-request Used for new features in Teleport, improvements to current should be #enhancements kube-operator Issues related to Kube Operator

Comments

@TeleLos
Copy link
Contributor

TeleLos commented Mar 2, 2023

What would you like Teleport to do?

Customer requesting that CRDs for the operator do not contain secret values. Examples include: password hashes, sso connectors

What problem does this solve?

The preference is to store this sensitive information as a Kubernetes secret then reference that secret when needed by the operator.

If a workaround exists, please include it.

None
@TeleLos TeleLos added feature-request Used for new features in Teleport, improvements to current should be #enhancements c-vo Internal Customer Reference kube-operator Issues related to Kube Operator labels Mar 2, 2023
@pschisa pschisa added the c-ca Internal Customer Reference label Mar 17, 2023
@webvictim webvictim mentioned this issue Jul 24, 2023
Closed
19 tasks
@programmerq programmerq added the c-aq Internal Customer Reference label Feb 29, 2024
@hugoShaka hugoShaka added the c-gy Internal Customer Reference label Mar 27, 2024
@zmb3
Copy link
Collaborator

zmb3 commented Oct 16, 2024

#46699

@zmb3 zmb3 closed this as completed Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c-aq Internal Customer Reference c-ca Internal Customer Reference c-gy Internal Customer Reference c-vo Internal Customer Reference feature-request Used for new features in Teleport, improvements to current should be #enhancements kube-operator Issues related to Kube Operator
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@programmerq @zmb3 @hugoShaka @pschisa @TeleLos