I have just updated the Kubernetes certs for a v7 deployment for a customer which is now all fine, however I noticed in WebSphere that the ElasticSearch certs actually expired in May. I tried to export new ones but still same date. I have never come across a deployment that has had this expire before. I would assume its because normally customers have upgraded. Anyone know how I get the self signed p12 re-issued in elastic search?
Hey Richard,
I summarized the update process here: https://stoeps.de/posts/2022/update-elasticsearch-certificates/
Cheers
Christoph
Hi Christoph,
Thanks for this that worked perfectly and the customers connections environment is all up and running again.
Hey there,
we also facing this issue.The elasticsearch-certificate is expired.
I did try to follow Christoph's Guide, but i am facing an issue in our environment. I did not find the bootstrap.yml on our system. Therefore, i am not able to install the the bootstrap again.
We did have a few restrictions on authorizations on the Kubernetes Systems. Therfore i have two question:
- Is there a default location where the bootstrap.yml is saved?
- Can i change this location while installing the bootstrap?
Best regards
Frederik
Usually the bootstrap.yml is saved in a directory, where all the config *.yml files are located. When you execute helm upgrade command for example:
helm upgrade bootstrap ~/path/to/local/helmcharts/bootstrap -i -f ~/path/to/bootstrap.yml --namespace $namespace
or
helm upgrade bootstrap v-connections-helm/bootstrap -i --version $version --namespace $namespace -f ~/path/to/bootstrap.yml
the bootstrap should be visible under jobs "kubectl get jobs -n $namespace"
Kind regards,
Petr