Closed vsawant1608 closed 3 months ago
Is this related to the question you asked here?
whose answer was:
Ah, it looks like you should probably just disable the networkPolicies.enabled flag in our Helm chart as ARO doesn't support Kubernetes egress policies out of the box, as discussed here.
You can set up egress firewall rules to control network traffic, but there's no requirement you run ASO with network policies enabled. They're on by default as a security best practice only. You can disable them (and write your own ARO-compliant ones if you'd like).
Closing this as it seems likely to be related to the issue which was already answered above.
Steps followed: Create ARO cluster. Deploy aso operator as per steps here https://azure.github.io/azure-service-operator/#create-the-azure-service-operator-namespaced-secret Tried creating resource.
Getting below error and unable to create any resource
resourcegroup looks like this