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

#210 (closed)

Upgrade Notices

N/A

Closes #210 (closed)

docs/DEVELOPMENT_MAINTENANCE.md

@@ -41,14 +41,12 @@ Chart.yaml](https://github.com/prometheus-community/helm-charts/blob/main/charts
 6. Generate the `README.md` updates by following the [guide in gluon](https://repo1.dso.mil/platform-one/big-bang/apps/library-charts/gluon/-/blob/master/docs/bb-package-readme.md).
     - Renovate bot may have already performed this step for you as well! 🤖
 
-7. If this is a new minor version of Elastic you will likely need to add a new section to `chart/templates/bigbang/upgrade-job.yaml` for the new version upgrade. Follow the existing examples to update the job to support upgrades between old version -> new version.
-
-8. Push up your changes, add upgrade notices if applicable, validate that CI passes.
+7. Push up your changes, add upgrade notices if applicable, validate that CI passes.
     - If there are any failures, follow the information in the pipeline to make the necessary updates.
     - Add the `debug` label to the MR for more detailed information.
     - Reach out to the CODEOWNERS if needed.
 
-9. As part of your MR that modifies bigbang packages, you should modify the bigbang  [bigbang/tests/test-values.yaml](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/tests/test-values.yaml?ref_type=heads) against your branch for the CI/CD MR testing by enabling your packages.
+8. As part of your MR that modifies bigbang packages, you should modify the bigbang  [bigbang/tests/test-values.yaml](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/tests/test-values.yaml?ref_type=heads) against your branch for the CI/CD MR testing by enabling your packages.
 
     - To do this, at a minimum, you will need to follow the instructions at [bigbang/docs/developer/test-package-against-bb.md](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/docs/developer/test-package-against-bb.md?ref_type=heads) with changes for Elasticsearch-Kibana enabled (the below is a reference, actual changes could be more depending on what changes where made to Elasticsearch-Kibana in the pakcage MR).