| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
4.2.1
Defined CPU consumption limit for the following services
Kafka
Elasticsearch
4.0.1
FIXES AND ENHANCEMENTS
Elasticsearch configuration UI improvements and bugfixes
4.0.0
ADDED
Enabled Elasticsearch for all clusters
Elasticsearch is planned to replace Postgres as the main data store for all products (including Synergy). We’re working to provide some degree of automation to update many clusters at once, but feel free to use latest 4.x version for manual upgrades if needed.
KNOWN ISSUES
Elasticsearch kind missing
When upgrading gv-essentials installed manually with Helm to version 4.x you may get the error Error: UPGRADE FAILED: unable to recognize "": no matches for kind "Elasticsearch"... .
This is because Helm cannot determine whether upgrading a CRD will break other things in the cluster, therefore, Helm v3 by design can create CRDs but is not able not upgrade them.
To address this issue install the CRDs manually:
| Code Block |
|---|
kubectl apply -f https://assets.master.k3s.getvisibility.com/k3s/misc/elastic.yaml |
In airgapped deployments, you can upload the elastic.yaml and run the following command before upgrading the chart:
| Code Block |
|---|
kubectl apply -f elastic.yaml |
Not enough memory
Wheen upgrading gv-essentials on a machine with 32 GB RAM via helm (without Rancher), Elasticsearch can get misconfigured to use 20 GB RAM, and the cluster will run out of memory. In this case, please amke sure you adjust the resource variables manually:
| Code Block |
|---|
helm upgrade --install gv-essentials gv_stable/gv-essentials --wait \
--timeout=10m0s --kubeconfig /etc/rancher/k3s/k3s.yaml \
--set eck-operator.enabled=true --set eck-operator.settings.cpu=1 \
--set eck-operator.settings.memory=1 |
Decreasing storage size is not supported: an attempt was made to decrease storage size for claim elasticsearch-data
A volume for ES data was already created in this cluster, and it’s larger than entered size. Current size can be checked in Storage -> Persistent Volumes -> elasticsearch-data-gv-es-default-0 or via kubectl get pv , but usually it's 160 GB.
For helm installations, use --set eck-operator.settings.disk=160 --set eck-operator.settings.storage=160
3.2.0
FIXES AND ENHANCEMENTS
Configured SaaS mode
3.1.2
FIXES AND ENHANCEMENTS
Actually disable heap dumps on OOM in Elasticsearch
3.1.1
FIXES AND ENHANCEMENTS
DIsabled heap dumps on OOM in Elasticsearch
3.1.0
FIXES AND ENHANCEMENTS
Upgrade Zalando Postgres Operator to version
1.10.0Make chart compatible with Kubernetes 1.25.x
KNOWN ISSUES
When upgrading gv-essentials to version 3.1.x you’ll get the error Error: UPGRADE FAILED: error validating "": error validating data... .
This is because Helm cannot determine whether upgrading a CRD will break other things in the cluster, therefore, Helm v3 by design can create CRDs but is not able not upgrade them.
...