Internally published OCP cluster

[swheettaos]

So I'm building and internally published cluster so no public loadbalancer in AWS. When I install the ODF, I get and error message saying

Error syncing load balancer: failed to ensure load balancer: could not find any suitable subnets for creating the ELB

when I find the service, for s3 and sts it does say external load balancer.

I also was just going to add the annotation like this:

service.beta.kubernetes.io/aws-load-balancer-internal: "true"

to it to see if it that would fix it .. but it warned me that it was managed by noobaa and might be overwritten.

Where can I change it so it uses the internal load balancer (I have endpoint services setup for that stuff so it's all reachable)

[swheettaos]

ok I verified by adding the annotation to the service fixes the problem .. is the best way to do it?

Also I don't need blob .. so is there a way to disable this?

[swheettaos]

Ok .. after RTFM ... lol... I see an "internal" mode for deployment, but I'm unsure how to do that in AWS. I don't know how to do it on an OCP cluster in AWS. Also, would this help with my LB issue? It sounds like the sts lb gets created so people can auth with the sts token to use the S3 blob (am I wrong with my assumption?). So I'd still like to know if there is a way to eliminate the external access. I'm only using block so I'm not sure what the s3/sts LBs are for.

[swheettaos]

Anyone? internally only published? or disable s3/sts because not needed?

[iamniting]

Hello @swheettaos,

Apologies for the delayed response due to the holidays.

The questions appear to be related to NooBaa. Could you please raise your queries in the NooBaa GitHub repository: https://github.com/noobaa/noobaa-operator?

Thank you!