Description
What happened:
Currently we don´t know if the ability to separate (from an existing nodepool) its subnet is supported, in a subnet for nodes and another for pods
What you expected to happen:
We want to have support for upgrading nodepools (dynamically) from it subnet toward a subnet for nodes and another subnet for pods, in the same vnet
How to reproduce it (as minimally and precisely as possible):
Does not apply in this case
Anything else we need to know?:
The nodepool of the workloads would be diferent from the system nodepool, in such a cluster
Environment:
Development, Test and Production
- Kubernetes version (use
kubectl version):
Probably by default or latest
- Size of cluster (how many worker nodes are in the cluster?)
Initially about 3 nodes for each cluster (development, testing and production)
- General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)
At the beginning stateless microservices for multiple purposes, although it could change in the future
- Others: