IBM Component Pack – quest for the missing elasticsearchsecret

Now the Customizer is up and running. Now I tried to put the elasticsearch stack. Following the IBM documentation, I was able to add a new worker node, dedicated solely for elasticsearch.
Putting the additional images in my dockerregistry, installing the helm charts. So far so good. But my es-master, es-data and es-client would not start. The log revealed the missing elasticsearch-secret. After some hints from Nico directing my search to the connections-env part. There’s parameter “createSecret=false” which drew my attention.

A short helm delete connections-env --purge and reinstall of the connections-env with createSecret=true did the trick.

One comment on “IBM Component Pack – quest for the missing elasticsearchsecret
  1. Сialis says:

    Good day! I could have sworn I’ve visited this site before but after going through many of
    the posts I realized it’s new to me. Anyhow, I’m definitely pleased I came across
    it and I’ll be book-marking it and checking back often!