Skip to content

chore: cleanup operator-framework-core pom #518

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.

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

Merged

Conversation

lburgazzoli
Copy link
Collaborator

No description provided.

@@ -61,12 +53,16 @@
<dependencies>
<dependency>
<groupId>io.fabric8</groupId>
<artifactId>openshift-client</artifactId>
<artifactId>kubernetes-client</artifactId>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should keep the OpenShift client here so that apps can get the more featured version if needed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really get this argument. Is there more features in openshift client?
This could be confusing for the users, at least shuold be documented. Also could be replaces in operators with maven if somebody want to use openshift client.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's more feature in the OpenShift client because it provides access to OpenShift-only resources in addition to the plain Kubernetes one. I don't think it causes any confusion as people can interact with this client the exact same way they would with the plain version. Replacing the client in not necessarily that trivial depending on how you do it and this is the easiest/simplest way to have broader support at this time.
Personally, I'd rather see the OpenShift client implemented as an add-on on top of the plain Kubernetes one but I'm not sure that's feasible at this point.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we put this there in form of a comment above this dependency for the users which are not necessary familiar with the relation of these clients?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can include a comment in this pr, what would you like me to add ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically what @metacosm mentioned. That "We use openshift client, because functionally it a superset of kubernetes client.". Thank you!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@lburgazzoli lburgazzoli force-pushed the operator-framework-core-cleanup branch from 1747556 to 604078e Compare August 30, 2021 08:03
@lburgazzoli lburgazzoli force-pushed the operator-framework-core-cleanup branch from 604078e to a44c965 Compare August 30, 2021 08:45
@metacosm metacosm merged commit b8433ed into operator-framework:master Aug 30, 2021
@metacosm metacosm deleted the operator-framework-core-cleanup branch August 30, 2021 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants