Enable Plans with Windows Worker Nodes
Page last updated:
Page last updated:
If you used Enterprise PKS Management Console to deploy Enterprise PKS with plans that implement Windows worker nodes, you must use Operations Manager to provide BOSH with a vSphere stemcell 2019.7 or later for Windows Server version 2019.
Enterprise PKS Management Console does not provide a mechanism for the automatic upload and installation of the Windows stemcell. Because Operations Manager and BOSH Director for vSphere are deployed when you deploy Enterprise PKS from Enterprise PKS Management Console, you can only install the stemcell after you have deployed Enterprise PKS.
After you deploy Enterprise PKS from the management console, any plans that use Windows worker nodes are ignored until you install a Windows Stemcell and configure the management console to use it.
Important: Support for Windows-based Kubernetes clusters is in beta and supports only vSphere with Flannel. You cannot use Windows worker nodes with NSX-T Data Center networking.
- You used Enterprise PKS Management Console to deploy Enterprise PKS with Flannel networking. For information about deploying Enterprise PKS from the management console, see Deploy Enterprise PKS by Using the Configuration Wizard. For information about how to configure Flannel networking, see Prerequisites for a Flannel Network.
- During Enterprise PKS deployment, you configured a plan that implements Windows worker nodes. For information about creating a plan with Windows worker nodes, see Configure Plans in Deploy Enterprise PKS by Using the Configuration Wizard.
- If you did not create a plan that uses Windows worker nodes when you deployed Enterprise PKS, or if you have upgraded Enterprise PKS Management Console from a version that did not support Windows worker nodes, you can use Enterprise PKS Management Console to reconfigure the plans of your existing deployment. For information about reconfiguring Enterprise PKS in the management console, see Reconfigure Your Enterprise PKS Deployment.
vSphere Windows Server stemcells are not available on the Pivotal Network. You must create vSphere Windows Server stemcells either manually or by using Stembuild and your own Windows Server ISO.
Create a Windows stemcell by following the instructions in Creating a Windows Stemcell for vSphere Manually or Creating a Windows Stemcell for vSphere Using stembuild (Beta).
After you have created your stemcell, you must upload it to Operations Manager and install it in BOSH. You can use either the Operations Manager interface or the Operations Manager CLI. These instructions describe how to upload and install the stemcell by using the Operations Manager interface.
- Log in to Operations Manager. For information about how to log in to Operations Manager and the credentials to use, see Log In to the Operations Manager UI.
- Select Stemcell Library.
- Click Import Stemcell and navigate to the location on your local machine where you saved the stemcell
.tgzfile in Step 1 above.
- Click Save.
After you have created a Windows stemcell and used Operations Manager to install it in BOSH Director for vSphere, you must redeploy your Enterprise PKS with the Windows stemcell installed.
- In Enterprise PKS Management Console, expand Configuration and select PKS Configuration.
- If you did not already create a plan that uses Windows worker nodes, or if you have upgraded this Enterprise PKS instance from a version that did not support Windows worker nodes, expand the Plans section and create or reconfigure a plan that uses Windows worker nodes.
- If necessary, reconfigure any other options that show a red status bar or that you want to change.
- Click Generate Configuration to view the generated YAML file.
- Click Apply Configuration to redeploy this Enterprise PKS instance.
- When the deployment finishes, go to the Enterprise PKS view and verify that the Windows Stemcell Status is INSTALLED.
You can now deploy Kubernetes clusters in plans that implement Windows worker nodes.
Please send any feedback you have to firstname.lastname@example.org.