-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
What I can see in EAP Operator ClusterServiceVersion
kind: ClusterServiceVersion metadata: name: eap-operator.v3.1.0 namespace: placeholder annotations: features.operators.openshift.io/disconnected: "false" features.operators.openshift.io/fips-compliant: "false" features.operators.openshift.io/proxy-aware: "false" features.operators.openshift.io/tls-profiles: "false" features.operators.openshift.io/token-auth-aws: "false" features.operators.openshift.io/token-auth-azure: "false" features.operators.openshift.io/token-auth-gcp: "false" capabilities: Seamless Upgrades
Acording to https://docs.openshift.com/container-platform/4.16/operators/operator_sdk/osdk-generating-csvs.html#olm-enabling-operator-for-restricted-network_osdk-generating-csvs point 5 it should be
Add the disconnected annotation, which indicates that the Operator works in a disconnected environment:
metadata:
annotations:
operators.openshift.io/infrastructure-features: '["disconnected"]'
Operators can be filtered in OperatorHub by this infrastructure feature.
