To summarize the VNG section, VNGs allow us to separate our workloads if needed, it allows us to have different node configurations in the cluster and expands the benefits Ocean provides.

We covered the usage of various Kubernetes constraints, we learned how we can use nodeSelectors or Affinity/Anti-Affinity rules to force the required node from the Pod side and how a node can repel Pods from being scheduled on top of it, most importantly we learned how we can use those types of constraints while utilising Ocean VNGs.

You can use the Launch API calls to manually launch additional nodes within the VNG (AWS, GKE, AKS)

(Currently only available for AWS) While using the API/Terraform, during the creation of a VNG you can define the initalNodes url param to specify the initial number of nodes required in the VNG.