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

Unable to replace SSL certificate with self signed #1448

Closed
kozlooo opened this issue Sep 9, 2024 · 2 comments
Closed

Unable to replace SSL certificate with self signed #1448

kozlooo opened this issue Sep 9, 2024 · 2 comments
Labels

Comments

@kozlooo
Copy link

kozlooo commented Sep 9, 2024

Looking for some advice, as have trying to fix dapr cert issue for a lot of hours.
Recently ran into issue that dapr was not restarted for more than year and all pods stopped working because of certificate was expired. To avoid such situations in future, I generated certificate (based on documentation) for 10 years and wanted to replace it in my k8s. This is the part which I can not achieve succesfully - as my company do not use sealed secrets, only option is secret provider from Azure keywault. I created mapping to secret dapr-trust-bundle, but after restarting sentry it gets overwritten to sentry certificate and later to secret provider, so that means they are conflicting. As I can see, there are option to paste certificates as plain text and place them in git (using gitops approach), but again, that is not something my colleauges from security team will be happy about.
Maybe someone can help with advice, what to do in such cases, how to solve them?

@dapr-bot
Copy link
Collaborator

dapr-bot commented Oct 9, 2024

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Oct 9, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants