Daniel Messer

The operator is packaged following a philosophy from the OpenShift Container Platform, which is to: - hard code container image references and not get those from external configuration - refer...

We could certainly look into that.

@DanArlowski Thanks for this submission. As you probably already noticed, the Quay Operator is undergoing some major re-design. It is managing the entire Kubernetes-level configuration in a very opinionated fashion...

Hm, I just tried it with the 3.8.10 operator on OCP 4.13 and it doesn't raise this issue. The `Deployment` just has resource request for CPU and RAM, but no...

This is not necessary because you can override the image at the platform level (I assume you are talking about disconnected OpenShift clusters).

Can you clarify what you refer to with `Service` resource and `Setup`?

@dmilewskiwph Thanks, now it tracks. The `Service` is normally deployed when you install the operator using OLM. If this has not happened, the corresponding `ClusterServiceVersion` and `InstallPlan` object should be...

+1 to @cgwalters points. I would add: - standardized way of providing and discovering provenance information to RPMs via OCI Referrers (beyond signatures also SBOMs, build attestations, etc), another example...

@Conan-Kudo I don't know that this is the primary goal, but as an owner of a very large public OCI registry service, I can tell you that I am much...

@kramvan1 OLM installs Operators on behalf of the user. The upside is that a user does not have to have all privileges that the Operator needs, the downside is that...