Skip to content

Conversation

@ktlim
Copy link
Contributor

@ktlim ktlim commented Jan 11, 2025

No description provided.

@ktlim ktlim requested a review from andy-slac January 11, 2025 00:21
Copy link

@andy-slac andy-slac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

- if you encounter an error like "Unable to connect to the server: No valid id-token, and cannot refresh without refresh-token" when running your kubectl, you will need to log back in via https://k8s.slac.stanford.edu/<project>, re-executing the commands in the second box. This is because our OIDC (dex) implementation does not and cannot generate refresh tokens from our SAML2 (windows ADFS) backend. (Actually, only the ``set-credentials`` command is needed, but it doesn't hurt to execute them all.)
- Kubernetes secrets are usually held in Vault (vault.slac.stanford.edu). The vault command is available on USDF interactive nodes. You may need to activate it with ``module load vault``.

Kubernetes secrets are usually held in Vault (vault.slac.stanford.edu). The vault command is available on USDF interactive nodes. You may need to activate it with ``module load vault``. Then login using the commands ``export VAULT_ADDR=https://vault.slac.stanford.edu; vault login -method=ldap`` with your SLAC Windows password. You can then use ``vault kv list -mount=secret PATH`` and ``vault kv get -mount=secret PATH/TO/SECRET`` to access secrets for which you have permission.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guessing what PATH may be another minor obstacle, and it looks like PATH is optional for list. maybe change it to kv list -mount=secret [PATH]?, or mention that PATH starts with rubin/?

@ktlim ktlim enabled auto-merge January 14, 2025 21:02
@ktlim ktlim merged commit 553c97a into main Jan 14, 2025
3 checks passed
@ktlim ktlim deleted the u/ktl/add-vault-cli branch January 14, 2025 21:05
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.

3 participants