Frederic Giloux

@acelinkit checking the latest version the port protocol has been added to [the manifests](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/deploy/upstream/quickstart/olm.yaml#L77), also [here](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/deploy/upstream/quickstart/olm.yaml#L77), last month. It should be part of the next release

@acelinkit thanks for taking the time and providing this valuable feedback.

Sorry to bring some negative perspectives but to me NetworkPolicy and kube-rbac-proxy, although both security related, do not address the same use case: - NetworkPolicy is for controlling network traffic...

Do you want to cover container registry authentication with this issue or create a separate one for it? This is often done with a kubernetes.io/dockerconfigjson secret.

Note: This is for local development environment.

@bnallapeta: - yes we need to wait for kcp 0.7 to fix the ingress issue - we then need to call what is provided in #117 as part of the...

@Roming22 this issue was specifically for ckcp. Things have evolved on the kcp side from envoy to kcp-glbc. I would see it as complete when kcp-glbc gets deployed with ckcp....

We will be fine with these ones as they get installed by default under the following namespaces: - openshift-operators-redhat - openshift-logging

Discussing with the kcp team: - A ServiceAccount is bound to the workspace it was created in - For this ServiceAccount to manipulate resources of other workspaces an APIExport for...

Sadly this is the first thing referenced in [the installation instructions](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/install/install.md)