Closed lionelmace closed 6 days ago
Hi @lionelmace - This is happening due to the variable disable_outbound_traffic_protection
taking the default value as false
. If you want to have this, you can open up outbound traffic by setting this variable to true
, for example as shown below:
This is not the only reason. Here is a full explanation of why it does not work after activating the outbound traffic.
We were able to recreate your problem not being able to display the content of the OperatorHub on a secure by default cluster. 1. On a new secure-by-default cluster with outbound traffic protection disabled during creation, it works. 2. On a new secure-by-default cluster with outbound traffic protection disabled AFTER creation (as you did), it fails. The problem is related to the OperatorHub being disabled. If you go to Administration > Cluster Settings > Configuration > OperatorHub, you can edit the Operator Hub and you you will see spec: disableAllDefaultSources: true To fix your issue run the command oc patch OperatorHub cluster --type json -p '[{"op": "remove", "path": "/spec/disableAllDefaultSources"}]' This is documented here https://cloud.ibm.com/docs/openshift?topic=openshift-sbd-allow-outbound#sbd-example-oh
I deployed the sample
basic
https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc/tree/main/examples/basicbut I cannot access the Operator Hub in the OpenShift console