Guy Margalit

Hey @ron1 OK, so the logs you attached show that we got disconnected from the DB. We've seen this symptom occurring mostly when low on cpu/memory resources, so lets start...

@hohoqq Thank you for reporting your experience! These addresses are used for internal cluster networking, not external, so the cluster name has nothing to do with those. See https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/. I...

@hohoqq I don't think it should be related to the cluster name. The `..svc.cluster.local` is expected to be available on any kubernetes for internal clients. You can try to look...

Thanks @hanqingwu I know that root doesn't have a kubeconfig, just wanted the CLI to avoid a panic in that case and write a clearer error message.

@nimrod-becker I think that #251 should resolve this one too.

Hi @davidkarlsen I am not sure exactly where you get this error exactly - are you using the noobaa cli to install or using ODF? Where is this error coming...

@davidkarlsen Did you take those CRDs directly from lib-bucket-provisioner by any chance? I see that they still host the CRD with apiextensions-v1beta1 here - https://github.com/kube-object-storage/lib-bucket-provisioner/blob/master/deploy/crds/objectbucket_v1alpha1_objectbucket_crd.yaml

@dannyzaken are you aware of such an issue with OCP?

@dannyzaken Maybe I'm missing something but isn't it an ODF operator installation? This is installed from operator hub in OCP right? How is this related to upstream lib-bucket-provisioner?

@ron1 I agree! The operator should sync both ways. We discussed it before but did not document it.