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

Find a way to grab the new certificate generated by Lets'encrypt to update our cluster (or a cluster) #365

Open
cmoulliard opened this issue Mar 4, 2024 · 0 comments · May be fixed by #366
Assignees
Labels
enhancement New feature or request

Comments

@cmoulliard
Copy link
Member

cmoulliard commented Mar 4, 2024

TODO

Find a way to grab the new certificate generated by Lets'encrypt to update our cluster (or a cluster)

Current procedure is:

  • Identify the VM running the certmanager and lets'encrypt for domain: snowdrop.dev
  • ssh to the VM and get the tls and key files
passstore-vm-ssh.sh openstack snowdrop-k8s
alias k=kubectl
k get secret/qshift-snowdrop-dev-tls -n snowdrop-site -ojson | jq -r '.data."tls.crt"' | base64 -d > tls.crt
k get secret/qshift-snowdrop-dev-tls -n snowdrop-site -ojson | jq -r '.data."tls.key"' | base64 -d > tls.key
  • Identify the ocp4 cluster where the console's certificate should be updated within the password store
  • scp the files to the target cluster
  • Recreate the secret used by ingress to access the ingress URL
alias k=kubectl
pass openstack/ocp-qshift-drp2b/kubeconfig > pki/kubeconfig
export KUBECONFIG=./kubeconfig
k -n openshift-ingress delete secret/qshift-console
k -n openshift-ingress create secret tls qshift-console --cert=pki/tls.crt --key=pki/tls.key # --dry-run="client" -oyaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants