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

Store Elasticsearch master certs (ca and key) into secret #320

Closed
3 tasks
pavolloffay opened this issue Mar 15, 2019 · 0 comments
Closed
3 tasks

Store Elasticsearch master certs (ca and key) into secret #320

pavolloffay opened this issue Mar 15, 2019 · 0 comments
Labels
Elasticsearch The issues related to Elasticsearch storage

Comments

@pavolloffay
Copy link
Member

pavolloffay commented Mar 15, 2019

We have to store ES master certs ca.crt, ca.key to a secret. These certs are needed to recreate client certs used by jaeger and curator.

The recreation of secrets happens on every loop. The script for creating the certs checks whether ca and key are present on operator's filesystem - if they are it uses them. The problem happens when the operator restarts - It will create new certs.

There is also other issue, we store certs in one directory at the moment so all instances get same ca and key certs.

The actions:

  • store master certs in a secret per instance
  • load master certs to filesystem before generating certs
  • set working directory for cert generation script to something which includes namespace and jaeger instance name
@pavolloffay pavolloffay added the Elasticsearch The issues related to Elasticsearch storage label Mar 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Elasticsearch The issues related to Elasticsearch storage
Projects
None yet
Development

No branches or pull requests

1 participant