Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Planning Guide—VMware Cloud Foundation 4.x on VxRail
Executive Summary VMware Cloud Foundation on VxRail VMware Cloud Foundation on VxRail Requirements and Use Cases VMware Cloud Foundation on VxRail Workload Domain Planning
Introduction
NSX-T management options for VI workload domain
vRealize software option for VI workload domains
vSphere with Kubernetes workload domains
Data Center and Network Requirements Cloud Foundation on VxRail High-Level Design Cloud Foundation on VxRail Workload Planning Application Dependencies and Routing Decisions Cloud Foundation on VxRail Physical Network Planning Cloud Foundation on VxRail Physical Network Preparation VxRail Cluster Deployment Preparation Prepare for VMware Cloud Foundation Management VI Workload Domain Prepare for Cloud Foundation VI Workload Domain Prepare for NSX-T Edge Gateway Services Prepare for Cloud Foundation Application Virtual Network Appendixes

vSphere with Kubernetes workload domains

vSphere with Kubernetes workload domains

  • SDDC Manager supports VI workload domain configurations that provide the infrastructure foundation required by vSphere with Kubernetes. A VI workload domain configured for Kubernetes transforms the vSphere platform into a platform for running Kubernetes workloads natively on the hypervisor layer. If there is a use case requirement for vSphere with Kubernetes, the following items must be considered:

    • All the nodes in the VxRail cluster supporting the VI workload domain must have a vSphere with Kubernetes license.
    • An NSX-T edge cluster must be available to the vSphere with Kubernetes workload domain for networking purposes.
    • The NSX-T edge cluster requires connectivity upstream using eBGP. Plan on preparing the upstream network for BGP peering and route distribution.
    • Additional IP addresses specific for vSphere with Kubernetes will be required when the VI workload domain is configured.
    • Non-routable subnet for pod networking (minimum /22)
    • Non-routable subnet for service IP addresses (minimum /24)
    • Routable subnets for ingress and egress for the NSX-T edge cluster (minimum /27).