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

[Xray] Random execution-service-aes-key breaks automation #1599

Closed
yaron opened this issue Mar 8, 2022 · 0 comments
Closed

[Xray] Random execution-service-aes-key breaks automation #1599

yaron opened this issue Mar 8, 2022 · 0 comments

Comments

@yaron
Copy link

yaron commented Mar 8, 2022

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):

helm template xray  -f values.yaml . > output.yaml
helm template xray  -f values.yaml . > output2.yaml
diff output.yaml output2.yaml 
246c246
<   execution-service-aes-key: "dThvNXpGb09JQWZ1WTdQdVU0NlZSamUxek8xbmFHYkc="
---
>   execution-service-aes-key: "MEZFS0NZNlJHYXhVZ0lpYmZqNVNWM05tUllWVW11R3U="

**Anything else we need to know**:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants