Revert to use the opster API's and onboard to OpenSearch universal release mechanism

[prudhvigodithi]

Description

Revert to use the opster API's and onboard to OpenSearch universal release process .

Issues Resolved

#709
#674

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[prudhvigodithi]

Hey @swoehrl-mw can you please take a look and add your review? looks to me like the functional tests are failing because of the image not able to get pulled.
Thanks
Adding @bbarani @peterzhuamazon

[swoehrl-mw]

@prudhvigodithi I suspect it's unable to pull the busybox image (for the init containers) as it does not yet exist.

[prudhvigodithi]

Next steps are:

• Onboard a jenkins job in https://build.ci.opensearch.org/ that uses the jenkins/release.jenkinsfile.
• Cut a tag with 2.5.0 which should trigger the above created job to build and push the docker images to ECR and dockerhub.
• The existing release.yaml will do a helm and github release.

@swoehrl-mw @bbarani @peterzhuamazon

[prudhvigodithi]

Thanks @swoehrl-mw and @peterzhuamazon, one more change, I dont think we need to build, push and maintain the busybox image separately , I have modified the logic to use the existing official busybox https://hub.docker.com/_/busybox, any concerns ?

[prudhvigodithi]

Yup all the tests pass now, merging the PR.

[swoehrl-mw]

I have modified the logic to use the existing official busybox https://hub.docker.com/_/busybox, any concerns ?

I believe it was only mirrored so that people would not potentially run into the dockerhub rate limits. But for most users this should not be a concern.

[prudhvigodithi]

Thanks I can change to ECR busybox https://gallery.ecr.aws/docker/library/busybox, as ECR has no rate limits for now.