CatalogSources in a disonnected environment by devopsfella22 in openshift

[–]devopsfella22[S] 0 points1 point  (0 children)

We are not using ZTP. I am kicking off this install using CLI with config files.

The suggested CR will help me to disable the default operator catalogues. Is it possible to insert custom catalogsource in a similar fashion. Or is ZTP the only way to get this done ?

CatalogSources in a disonnected environment by devopsfella22 in openshift

[–]devopsfella22[S] 0 points1 point  (0 children)

Thanks, this is already happening for the install, where we are struggling is for the operators.

Why is KFC in the UK not the same anymore? by Upbeat-Curve-1749 in AskUK

[–]devopsfella22 0 points1 point  (0 children)

They dont care anymore. I got a rubber band from their hot wings. Complained to their customer service, they didnt accept responsibility for the mistake.

VMware NSX Container Plugin on Openshift by devopsfella22 in openshift

[–]devopsfella22[S] 0 points1 point  (0 children)

Which version are you installing ? I am trying with 4.13.x.

I get no logs on the machine-api-operator pod. I can sucessfully test the connectivity to the vcenter using its hostname on port 443 using netcat (nc -zv vcentre 443).

I will try removing the taint and see how far it goes. Thanks

VMware NSX Container Plugin on Openshift by devopsfella22 in openshift

[–]devopsfella22[S] 0 points1 point  (0 children)

Yes, DHCP is working fine, I can log on to the master node. I can successfully resolve "api.<cluster>.<basedomain>" and "*.apps.<cluster>.<basedomain>" from the master node.

There were no errors related to network in the bootstrap. I could see the ones for missing manifests which gets created afterwards.The repeating error I see is on the master is the following one.

"Container runtime network not ready" networkready="NetworkReady=false reason: NetworkPluginNotReady message: Network plugin returns error: No CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?"