operator
operator copied to clipboard
tektoncd
Why are OpenShift images based on RHEL8 instead of UBI8?
Feature request
Using images based on UBI: like registry.access.redhat.com/ubi8/buildah instead of images based on RHEL8 like: registry.redhat.io/rhel8/buildah
Use case
Images based on RHEL8 are bound to RHEL EULA, which limits redistribution. This restriction does not apply to UBI8 images. A consequence is that registry.redhat.io requires authentication. registry.access.redhat.com does not. Images based on RHEL8 need to run on machines having RHEL subscriptions. This is not the case for UBI8 images.
@fgiloux 🤔 I think the image used by the operator (upstream) with the OpenShift target is ubi8 (see https://github.com/tektoncd/operator/blob/main/.ko.yaml).
This is indeed not the case for the "downstream" operator, aka OpenShift Pipelines, as it is a requirement for us to be able to have our customer get support.
In a gist, upstream OpenShift release such as here should use ubi8, but OpenShift Pipelines release (available through the OpenShift specific Operator Hub) are using RHEL8 by design.
Note: if upstream OpenShift release such as here are using RHEL, then this should be considered as a bug.
Ah it's only for few images, such as the buildah image, I see. Then I tend to agree.
I've checked, all of the component and operator images are based on top of ubi8, only few like the buildah one are not.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
tektoncd/operator is gonna change a bit early 2023 and the openshift part will be split, but it's still a valid point to fix indeed.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./close
Send feedback to tektoncd/plumbing.
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/test-infra repository.