Regenerate utoronto kubernetes cluster credentials #3492
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looks like this may have expired. This was regenerated with:
az login
, and logging into Azure with appropriate credentialssops -i -d <path-to-credential-file>
, to decrypt the credentialsexport KUBECONFIG=<path-to-credential-file>
, to tellkubectl
to use our checked in credentials. You can test that the credentials no longer work withkubectl get node
- you should get an error message about authorizationaz aks list -o table
az aks get-credentials --name <resource-group> --resource-group <resource-group>
. For the utoronto cluster, this isaz aks get-credentials --name=hub-cluster --resource-group 2i2c-utoronto-cluster
. You may be asked if you want to overwrite the current credentials - answer 'yes'.sops -i -e <path-to-credential-file>
.