Release v2.0.0-rc.0

[ChenYi015]

Purpose of this PR

Release Spark operator v2.0.0-rc.0.

Given that this is the first version of Spark Operator after improving the release process #2089, let me elaborate on the details:

1. Upon merging this PR, a Git tag corresponding to the version specified in the VERSION file (specifically, v2.0.0-rc.0) will be automatically created and pushed, provided it does not already exist.
2. Following the git tag's push, one workflow detailed in release-docker.yaml will be triggered to publish the Docker image with tag 2.0.0-rc.0(without prefix v).
3. Concurrently, another workflow detailed in release.yaml will be triggered to create a draft release, with the helm chart packaged as a artifact.
4. Then, we will edit the release notes and finally publish the release.
5. Once the release is published, one workflow detailed in release-charts.yaml will be triggered to update the Helm repo index file index.yaml.

[ChenYi015]

/hold
/assign @yuchaoran2011 @vara-bonthu @andreyvelich

[vara-bonthu]

/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vara-bonthu, yuchaoran2011

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vara-bonthu,yuchaoran2011]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ChenYi015]

/hold cancel

[ChenYi015]

Hi @andreyvelich. I had met some problems while releasing Spark operator. After this PR was merged, the tag v2.0.0-rc.0 was successfully created and pushed by the workflow. However, another two workflows release-docker.yaml and release.yaml were not triggered by this tag push event as expected. And I cannot figure out why, perhaps you could offer me some guidance.

[andreyvelich]

Hi @andreyvelich. I had met some problems while releasing Spark operator. After this PR was merged, the tag v2.0.0-rc.0 was successfully created and pushed by the workflow. However, another two workflows release-docker.yaml and release.yaml were not triggered by this tag push event as expected. And I cannot figure out why, perhaps you could offer me some guidance.

@ChenYi015 It looks like according to this one GitHub workflow can't trigger another GitHub workflow: https://github.com/orgs/community/discussions/27028#discussioncomment-3254360

We might need to refactor our test to publish images in the same workflow where we push tag to the GitHub.
WDYT @ChenYi015 ?

[ChenYi015]

@andreyvelich Thanks for your help. I agree with you and I will refactor the workflows and put them in one workflow file. For the release of v2.0.0-rc.0 version, since the VERSION file has already been modified, we will delete the tag and push it again manually to trigger the workflows to publish the docker image and draft the release.