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

Where is the subsititute for "operatorsource" #2854

Closed
LronDC opened this issue Sep 7, 2022 · 2 comments
Closed

Where is the subsititute for "operatorsource" #2854

LronDC opened this issue Sep 7, 2022 · 2 comments

Comments

@LronDC
Copy link

LronDC commented Sep 7, 2022 •
edited
Loading

Question

What did you do?
I searched old PRs and also the latest master, and noticed that operatorsource had been removed #651

What did you expect to see?
I want to know since operatorsource had been removed, how does OLM or Operator Framework connect to the outside or say online resources? Did operatorsource be somewhere else in Operator Framework?

What did you see instead? Under which circumstances?
I've also noticed that operator-marketplace added and removed operatorsource too. I want to know the intention of doing so.
@dmesser
Copy link
Contributor

dmesser commented Sep 7, 2022

OperatorSource served as an indirection of making operator's available to installs from a source like CatalogSource. CatalogSource is now the canonical API to bring collections of operators and their version history into the cluster.

The operator-marketplace concept was providing an additional layer of filtering what's available to install from a catalog. User feedback was that this did not serve a particular use case and it was easier to just use CatalogSource directly. Hence the removal.

Did you have a use case for OperatorSource outside of that?

@LronDC
Copy link
Author

LronDC commented Sep 8, 2022 •
edited
Loading

Did you have a use case for OperatorSource outside of that?

Well, actually no. But I do like the possibility to have an additional layer of filtering what's available to install from a catalog.
So I was wondering.
Thanks for the explanations.

@LronDC LronDC closed this as completed Sep 8, 2022
anik120 added a commit to anik120/operator-lifecycle-manager that referenced this issue Sep 14, 2022
@anik120
(psa) add unit test cases for registry pod config
aa6435a 
This PR adds unit tests to test the pod+container securityContext configs
introduced in operator-framework#2854
@anik120 anik120 mentioned this issue Sep 14, 2022
Merged
11 tasks
anik120 added a commit to anik120/operator-lifecycle-manager that referenced this issue Sep 14, 2022
@anik120
(psa) add unit test cases for registry pod config
e89aeba 
This PR adds unit tests to test the pod+container securityContext configs
introduced in operator-framework#2854

Signed-off-by: Anik Bhattacharjee <[email protected]>
anik120 added a commit to anik120/operator-lifecycle-manager that referenced this issue Sep 15, 2022
@anik120
(psa) add unit test cases for registry pod config
bda476d 
This PR adds unit tests to test the pod+container securityContext configs
introduced in operator-framework#2854

Signed-off-by: Anik Bhattacharjee <[email protected]>
openshift-merge-robot pushed a commit that referenced this issue Sep 15, 2022
@anik120
(psa) add unit test cases for registry pod config (#2860)
71f128a 
This PR adds unit tests to test the pod+container securityContext configs
introduced in #2854

Signed-off-by: Anik Bhattacharjee <[email protected]>

Signed-off-by: Anik Bhattacharjee <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dmesser @LronDC