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

When cert expires on commerce backend, the pod ends up taking the old certificate, instead of the newly generated one. #20

Open
L1ghtman2k opened this issue Dec 1, 2021 · 2 comments

Comments

@L1ghtman2k
Copy link
Member

Due to how we are loading cert in the backend, the renewal of the cockroach cert doesn't apply correctly to this workload. We should look for a better, more native approach of loading the cert into the pod.

@L1ghtman2k
Copy link
Member Author

Current workaround when cert expires:

  • save commerce backend's manifest file
  • Delete the workload completely kubectl delete deployment ...commerce-backend...
  • Recreate using the saved file

This process ensures that the volumes now contain the most up-to-date cert

@L1ghtman2k
Copy link
Member Author

Same applies to cockroach client

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