Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Delete operators/hazelcast-platform-operator #4638

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Delete operators/hazelcast-platform-operator #4638

wants to merge 1 commit into from

Conversation

devOpsHelm
Copy link
Contributor

New Hazelcast Platform Operator will be published on certified-operators and community-operators-prod is no longer maintained.

New Submissions

Your submission should not

  • Add more than one operator bundle per PR
  • Modify any operator
  • Rename an operator
  • Modify any files outside the above mentioned folders
  • Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

  1. Description of the managed Application and where to find more information
  2. Features and capabilities of your Operator and how to use it
  3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

  • Human readable name and 1-liner description about your Operator
  • Valid category name1
  • One of the pre-defined capability levels2
  • Links to the maintainer, source code and documentation
  • Example templates for all Custom Resource Definitions intended to be used
  • A quadratic logo

Remember that you can preview your CSV here.

--

1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need

2 For more information see here

@rh-operator-bundle-bot
Copy link
Contributor

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run4pd48
Start Time: 2024-06-06 21:47:35+00:00

Tasks

Status Task Start Time Duration
✔️ get-pr-number 2024-06-06 21:47:37+00:00 7 seconds
✔️ acquire-lease 2024-06-06 21:47:48+00:00 7 seconds
✔️ set-github-started-label 2024-06-06 21:47:59+00:00 7 seconds
✔️ set-github-status-pending 2024-06-06 21:48:10+00:00 8 seconds
✔️ set-env 2024-06-06 21:48:20+00:00 8 seconds
✔️ clone-repository 2024-06-06 21:48:33+00:00 31 seconds
✔️ clone-repository-base 2024-06-06 21:48:33+00:00 32 seconds
❌ detect-changes 2024-06-06 21:49:07+00:00 58 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/f21f335c2fcc0087c20d68346a073c70

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

@devOpsHelm devOpsHelm force-pushed the delete-hazelcast-platform-operator branch from d4fdc8e to a48d8ba Compare June 6, 2024 21:53
@rh-operator-bundle-bot
Copy link
Contributor

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runcm226
Start Time: 2024-06-06 21:53:41+00:00

Tasks

Status Task Start Time Duration
✔️ get-pr-number 2024-06-06 21:53:43+00:00 7 seconds
✔️ acquire-lease 2024-06-06 21:53:54+00:00 8 seconds
✔️ set-github-started-label 2024-06-06 21:54:04+00:00 9 seconds
✔️ set-github-status-pending 2024-06-06 21:54:15+00:00 8 seconds
✔️ set-env 2024-06-06 21:54:26+00:00 6 seconds
✔️ clone-repository 2024-06-06 21:54:35+00:00 37 seconds
✔️ clone-repository-base 2024-06-06 21:54:36+00:00 33 seconds
❌ detect-changes 2024-06-06 21:55:15+00:00 58 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/52643f0f292c9de2df35229936c1787d

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

@devOpsHelm
Copy link
Contributor Author

Hello, @mvala @J0zi @mporrato @Allda
Please take a look on this PR and merge it.
New Hazelcast Platform Operator will be published on certified-operators and community-operators-prod is no longer maintained.

@mporrato
Copy link
Collaborator

As per #3679 , removal and modification of existing bundles is no longer supported by the community pipeline.

@hasancelik
Copy link
Contributor

@mporrato, I acknowledge the policy, but we don't just want to remove one bundle version; we want to remove the entire listing. We won't be releasing a new version of this bundle, as mentioned earlier. We don't want to list the unsupported version of our bundle on the OCP OperatorHub dashboard. How can we achieve this?

@mporrato
Copy link
Collaborator

That involves removing the existing bundles too, which is not supported.

@hasancelik
Copy link
Contributor 

We don't want to list the unsupported version of our bundle on the OCP OperatorHub dashboard.

Do you have any solutions or advice for that? We do not want to list the old version of the bundle, which is not maintained by us anymore.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 5, 2024
@openshift-merge-robot
Copy link

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Allda
Copy link
Collaborator

Allda commented Aug 14, 2024

@hasancelik We are about to release a support of FBC (file-based catalog) for community operators where a removal action will be allowed. Would you be okay with joining the FBC once it is ready and trying to remove the operator using the new workflow? Since you want to remove the operator this could be a good candidate for FBC acceptance testing.

@Allda
Copy link
Collaborator

Allda commented Aug 27, 2024

@hasancelik I did an initial step to convert the operator to FBC which will allow you to remove it. Here is a PR with draft changes. Please review it and approve if you agree with the changes. Once it is approved and merged you will be able to remove the operator.
#5035

@hasancelik
Copy link
Contributor

@Allda We have already fully deprecated our operator with 5.13.1 release:
#4904

To clarify, from what I understand, will our bundles be completely removed from the operatorhub dashboard with your PR (#5035)?

@Allda
Copy link
Collaborator

Allda commented Aug 28, 2024

@Allda We have already fully deprecated our operator with 5.13.1 release: #4904

To clarify, from what I understand, will our bundles be completely removed from the operatorhub dashboard with your PR (#5035)?

Yes, you will be able to remove it completely from all places. Once my PR is merged you can then remove a whole content from the repository without failing a pipeline. This step will remove it from the git repo and operator hub.

@cheels
Copy link
Contributor

cheels commented Sep 9, 2024

Hello @Allda I just noticed that you forgot to add 5.13.0 and 5.13.1 versions to remove. Could you please add these 2 versions:

We added 5.13.1 as a patch to notify customers that it was deprecated but since you are introduce the removal action we cat remove it completely.

Thanks!

@Allda
Copy link
Collaborator

Allda commented Sep 18, 2024

@cheels If you want an operator to be removed you need to first approve a conversion to a FBC. You can do it by giving me 👍 to this PR. #5035

@cheels cheels mentioned this pull request Nov 6, 2024
Draft
21 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. operator-hosted-pipeline/failed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@devOpsHelm @rh-operator-bundle-bot @mporrato @hasancelik @openshift-merge-robot @Allda @cheels