-
Notifications
You must be signed in to change notification settings - Fork 719
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
GCS Repository plugin not loading #1349
Comments
Hello, Can you share the resource definition you used to try to reproduce the issue and the full log error (starting by a timestamp)? |
This is the resource definition
and the full log error
|
I think the issue is caused because Elasticsearch expects the value of the You can compact JSON using jq -cM . jsonfile > compactedjsonfile |
Is there a way elastic operator can be be correct to take in non-compacted json key as we generate the json key through terraform. If not possible let us know we will proceed with the alternative through terraform. |
Thank you for noticing this! I've investigated and found that we changed this behaviour when we changed the way the secure settings are added to the Elasticsearch keystore (#1221). Before, the version that works with uncompacted JSON:
Now, the version that works only with compacted JSON:
I have to check but I think we could go back to the previous version so that you have nothing to do on your side. |
Given it's convenient to not use `--stdin` with the ES keystore to fix elastic#1349, this commit makes the keystore settings addition different for ES than for Kibana and the APM Server. Only the Elasticsearch keystore supports settings additions using a file path. Kibana and APM Server supports only to pass the value through stdin and use the --stdin flag.
Given it's convenient to not use `--stdin` with the ES keystore to fix #1349, this commit makes the keystore settings addition different for ES than for Kibana and the APM Server. Only the Elasticsearch keystore supports settings additions using a file path. Kibana and APM Server supports only to pass the value through stdin and use the --stdin flag.
Given it's convenient to not use `--stdin` with the ES keystore to fix elastic#1349, this commit makes the keystore settings addition different for ES than for Kibana and the APM Server. Only the Elasticsearch keystore supports settings additions using a file path. Kibana and APM Server supports only to pass the value through stdin and use the --stdin flag.
Given it's convenient to not use `--stdin` with the ES keystore to fix #1349, this commit makes the keystore settings addition different for ES than for Kibana and the APM Server. Only the Elasticsearch keystore supports settings additions using a file path. Kibana and APM Server supports only to pass the value through stdin and use the --stdin flag.
Bug Report
What did you do?`
Used elastic search operator
docker.elastic.co/eck/eck-operator:0.9.0-rc3
. And add initcontainer to install gcs plugin as per https://github.com/elastic/cloud-on-k8s/blob/master/docs/snapshots.asciidoc.What did you expect to see?
All the efk-es pods starting up correctly.
What did you see instead? Under which circumstances?
Errors in starting the pod, because of issues in loading the GCS plugin
This issue is explained in https://discuss.elastic.co/t/error-to-setup-google-cloud-storage-service-auth/142823
Environment
Version information:
eck-operator:0.9.0-rc3
Kubernetes information:
$ kubectl version
The text was updated successfully, but these errors were encountered: