forked from elastic/cloud-on-k8s
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Changes to operator hub tooling for 2.9 release (elastic#7056) (elast…
…ic#7059) I realised while looking at https://github.com/k8s-operatorhub/community-operators/tree/main/operators/elastic-cloud-eck/2.8.0/metadata that the format for the community operator submissions has changed to bundle format. I am not sure if a submission is still possible in legacy package format once the previously published versions have been (auto-) converted to bundles. This change - moves the manifest generation to bundle format - removes all the "extra" functions in the bundle PR submissions code - renaming of the CSV is not necessary if we just don't generate the version into the name to begin with. The registry seems to look at Kind anyway to identify CSVs - the image SHA replacement code was dead and duplicating the working code in the manifest generation - the *package.yaml thingy is no longer needed in bundle format - removes the bundle generate command which is not necessary if we template in bundle format to start with. (cherry picked from commit cc201b7) # Conflicts: # hack/operatorhub/config.yaml # hack/operatorhub/go.sum
- Loading branch information
Showing
12 changed files
with
87 additions
and
888 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.