-
Notifications
You must be signed in to change notification settings - Fork 902
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
docs(docker): remove UBI #2720
docs(docker): remove UBI #2720
Conversation
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥲
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, jasondellaluce, leogr, LucaGuerra 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:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
/kind documentation
What this PR does / why we need it:
Since the CNCF has never provided us with an answer regarding potential IP policy issues regarding the usage of the UBI image in a CNCF project, and since the image has never been published nor officially released, the core maintainers in the last 2023-08-03 meeting decided to remove this Docker files for now. This is also part of a general effort to clean-up less used or unnecessary third-party dependency.
We may want to reintroduce the UBI-based image in the future as long as we find a way to make sure there are no licensing issues before reintroducing it.
Special notes for your reviewer:
/milestone 0.36.0
Does this PR introduce a user-facing change?: