Issue passing CIDR values in cluster config

#1

With Gravity 5.5.7, I’m having trouble setting up the cluster config to use a service CIDR port range.

I have the following config file:

kind: ClusterConfiguration
version: v1
spec:
    global:
      # represents the IP range from which to assign service cluster IPs
      serviceCIDR:  "172.45.0.0/16"
      # CIDR range for Pods in cluster
      podCIDR: "172.23.0.0/16"

But when I run gravity install and pass in the --config=cluster-config.yaml file, it ends up blowing up at the Wait for cluster to pass health checks stage. If I manually try do a kubectl command, I get:

# kubectl get pods --all-namespaces
Unable to connect to the server: x509: certificate is valid for 127.0.0.1, 127.0.0.2, 10.1.10.73, 10.100.0.1, not 172.45.0.1

Which seems to match the serviceCIDR setting above and it’s causing problems.

Interestingly, if I pass the same flags on the command line - --pod-network-cidr="172.23.0.0/16" --service-cidr="172.45.0.0/16" - it works just fine and everything starts up as expected.

Any ideas what the issue might be?

#2

Thanks for reporting this, one of our engineers is looking at this, will update the post.

#3

Thanks Sasha. I’ve actually found several other issues (I also opened a PR for one of them on gravitational/planet). Should I file the ones that are clearly bugs on GitHub?

#4

Sure, if you are confident that this is a bug, feel free to create an issue.