-
Notifications
You must be signed in to change notification settings - Fork 659
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
Labels
Comments
As, I have not worked with Kubernetes before , Please guide me to how to start to debug the issue. |
Hey @imrajdas ! do we need move it to under secret resource?
|
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. |
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we are storing CUSTOM_TLS_CERT in a configmap-
litmus/litmus-portal/graphql-server/manifests/cluster/3b_agents_deployment.yaml
Line 13 in c6cda32
subscriber-secret
secretThe text was updated successfully, but these errors were encountered: