Are Pods always assigned to `10.244.0.0/16`?

Hello @caffeinestorm,

Firstly, congratulations on spinning up a managed Kubernetes cluster and deploying your workloads! 🎉

To address your question on the cluster_subnet:

1. Is the cluster_subnet always 10.244.0.0/16?

   • As of now, the overlay network does utilize the 10.244.0.0/16 CIDR. However, it’s crucial to understand that this is an implementation detail that can change based on the needs or updates in the platform. Thus, it’s not advisable to rely on this specific range for any of your configurations or operations.

2. If I spin up a new cluster, am I guaranteed a cluster_subnet of 10.244.0.0/16?

   • There’s no guarantee. While currently the clusters are being assigned this range, future versions or updates might differ. Relying on this specific CIDR might cause issues during potential upgrades.

3. Can I choose a different cluster_subnet during cluster creation?

   • Currently, there isn’t an option for users to specify a custom cluster_subnet range during the cluster creation process.

A significant point to remember is that in DOKS (DigitalOcean Managed Kubernetes), there are more efficient and robust mechanisms to identify workloads beyond just IPs. It’s advisable to leverage those mechanisms to ensure the resilience and stability of your deployments.

For example, one option here is to use a service. A Kubernetes Service is an abstraction that defines a logical set of pods and a way to access them. When creating a service, Kubernetes will allocate a unique IP address (ClusterIP) which remains static for the lifecycle of the service. This means that you don’t have to rely on the individual IPs of pods, but rather on the Service’s ClusterIP or its DNS name.

I hope this clarifies your queries. Please let us know if you have any other questions or need further assistance!

Best,

Bobby