Resolve "Elasticsearch AutoRollingUpgrade is getting error"
General MR
Summary
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.
Relevant logs/screenshots
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
Linked Issue
Upgrade Notices
N/A
Closes #210 (closed)
Merge request reports
Activity
added elasticsearch kindbug priority5 statusreview teamObservability labels
requested review from @blairbowden, @kliu, @kscheunemann, @piotr.machaj, @steven.donald, and @peter.sigur
assigned to @zcallahan
- Automatically resolved by Zach Callahan
added 1 commit
reset approvals from @kliu by pushing to the branch
enabled an automatic merge when the pipeline for d9cf24e8 succeeds
mentioned in commit 7ae49dca
mentioned in merge request big-bang/bigbang!5178 (merged)