Daniel Messer
Daniel Messer
So, should we just clarify the guidance in the spec to say something along the lines of "must accept any `mediaType` and as result, should support nested indexes" ?
Makes sense. Would it be wrong if we get more specific about the expected behaviors of clients vs. registries at this particular point in the spec?
Curious, what use case does this address?
Wouldn't this question be best answered from the perspective of an operator configured / scoped via an `OperatorGroup` ? I.e. instead of listing the `OperatorGroup` themselves, which are sort of...
I guess I am trying to understand the situation in which a user would use this command. It's not obvious to me. Let's say I want to install an operator...
I feel proposal 1 is the cleanest approach as it has good CLI UX and clear expectation setting. Trying to manage v1 and v0 based operator deployments with the plugin...
The helm chart and quick start YAML is currently not maintained. We do offer an `install.sh` as part of GitHub releases but you can also get the required YAML directly...
@souleb can you expand on the use case for adding a `ResourceQuota` to a bundle?
@souleb That's an interesting use case. I think so the operator bundle design assumes that operators are optional components that do not require a special priority or is part of...
Not sure this qualifies as a bug, but definitely a valid point.