You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Which chart:
Xray helm chart > 103.43.1
What happened:
When using argocd to continuously check the helm chart and keep it in sync it tries to change the execution-service-aes-key key every time it runs. This is because the key is randomly generated every time it runs.
What you expected to happen:
To create a "changeme" value that can be changed in the values.yaml just like the joinkey and masterkey.
How to reproduce it (as minimally and precisely as possible):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Which chart:
Xray helm chart > 103.43.1
What happened:
When using argocd to continuously check the helm chart and keep it in sync it tries to change the execution-service-aes-key key every time it runs. This is because the key is randomly generated every time it runs.
What you expected to happen:
To create a "changeme" value that can be changed in the values.yaml just like the joinkey and masterkey.
How to reproduce it (as minimally and precisely as possible):
The text was updated successfully, but these errors were encountered: