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

Move the CUSTOM_TLS_CERT from subscriber config to subscriber secret #3943

Open
imrajdas opened this issue Apr 7, 2023 · 3 comments · May be fixed by #4263 or #4291
Open

Move the CUSTOM_TLS_CERT from subscriber config to subscriber secret #3943

imrajdas opened this issue Apr 7, 2023 · 3 comments · May be fixed by #4263 or #4291
Labels

Comments

@imrajdas
Copy link
Member

imrajdas commented Apr 7, 2023

Currently, we are storing CUSTOM_TLS_CERT in a configmap-

move this to subscriber-secret secret

@JAYESHBATRA
Copy link

As, I have not worked with Kubernetes before , Please guide me to how to start to debug the issue.

@afzal442
Copy link

Hey @imrajdas ! do we need move it to under secret resource?

@RipulHandoo
Copy link
Contributor

Hello @neelanjan00 @gdsoumya, I've reviewed the modifications you both suggested in this pull request. Since it has been open for the last 6 months, I've submitted a new pull request to address these changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment