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.

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

Secrets management #73

Open
salexo opened this issue Jan 31, 2025 · 0 comments
Open

Secrets management #73

salexo opened this issue Jan 31, 2025 · 0 comments

Comments

@salexo
Copy link
Contributor

salexo commented Jan 31, 2025

From @markvanheeswijk

the secrets and other things that may or may not come (or be assumed in the environment) are a bit problematic currently.
e.g. secrets:

  • can workload assume they have been applied in the namespace?
  • under what names?
  • are they per-user or per-usergroup? e.g. does a user take his own hf-token or is there one on an org-level?
  • if we cannot assume they exist or know the names, we need to create them
    • before the workload (but then we need to know ClusterSecretStore details, and keys of external secrets to pull in
    • during the workload submission (but then we need easy way to apply multiple manifests, so we don't have to put them in single custom template file)
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

No branches or pull requests

1 participant