Resolve "Elasticsearch AutoRollingUpgrade is getting error"
- Oct 01, 2024
-
-
Zach Callahan authored
-
- Sep 30, 2024
-
-
Zach Callahan authored
-
Zach Callahan authored
-
Zach Callahan authored
-
Zach Callahan authored
-
UNCLASSIFIED - NO CUI
Currently supported Big Bang Version is 2.49
Attention Iron Bank Customers: On March 27, 2025, we are moving SBOM artifacts from the Anchore Scan job to the Build job to streamline the container hardening pipeline. If you currently download SBOMs from the Anchore Scan job, you can still get them from the Build job and from other sources, including IBFE and image attestations.
This MR, though originally intended to "fix" the elastic upgrade job, is actually removing the job altogether. The job is unnecessary as the ECK operator (which this package depends on) already handles upgrade logic for ElasticSearch and Kibana instances deployed via its CRDs.
After an upgrade from 1.18.0-bb.5
to 1.19.0-bb.1
with autoRollingUpgrade.enabled
set to false
:
❯ kubectl get es -n logging
NAME HEALTH NODES VERSION PHASE AGE
logging-ek green 7 8.15.1 Ready 100m
❯ kubectl get pod -n logging
NAME READY STATUS RESTARTS AGE
logging-ek-es-data-0 2/2 Running 0 62m
logging-ek-es-data-1 2/2 Running 0 64m
logging-ek-es-data-2 2/2 Running 0 66m
logging-ek-es-data-3 2/2 Running 0 69m
logging-ek-es-master-0 2/2 Running 0 54m
logging-ek-es-master-1 2/2 Running 0 57m
logging-ek-es-master-2 2/2 Running 0 59m
logging-ek-kb-55865bdcf-46ptm 2/2 Running 0 54m
logging-ek-kb-55865bdcf-df2tp 2/2 Running 0 54m
logging-ek-kb-55865bdcf-ktrjt 2/2 Running 0 54m
N/A
Closes #210 (closed)
UNCLASSIFIED - NO CUI