[Beta] Windows worker cluster creation in Enterprise PKS fails with bosh-dns-windows job

Products

• VMware

Issue/Introduction

Symptoms:

• Windows worker cluster creation fails with bosh-dns-windows job.

• In the bosh task logs, you see the entries similar to:
  Task 73 | 15:03:14 | Updating instance master: master/b70f1851-6757-47b9-acaa-155893f429bb (2) (00:02:59)
  Task 73 | 15:06:13 | Updating instance worker: worker/a3842eed-3aff-4280-961d-115322d8db92 (0) (canary) (00:06:35)
  Task 73 | 15:12:48 | Updating instance windows-worker: windows-worker/68ce070a-6dd1-4823-8bf4-51533f832ddb (0) (canary) (00:01:49)
  Task 73 | 15:14:37 | Updating instance windows-worker: windows-worker/801d9a92-d9e8-4525-b700-f2fc7b773b41 (2) (00:01:55)
                    L Error: Action Failed get_task: Task 4d5b82d0-d8d9-4caf-73a4-49c8f43ce187 result: 1 of 1 post-start scripts failed. Failed Jobs: bosh-dns-windows.
  Task 73 | 15:16:32 | Error: Action Failed get_task: Task 4d5b82d0-d8d9-4caf-73a4-49c8f43ce187 result: 1 of 1 post-start scripts failed. Failed Jobs: bosh-dns-windows.

Environment

VMware PKS 1.x

Cause

This issue occurs if you misconfigure the Kubernetes Service network in the Networking section under PKS tile.

For Windows worker-based clusters the Kubernetes Service Network CIDR Range setting must remain 10.220.0.0/16. For more information, see Networking section under Configuring Windows Worker-Based Kubernetes Clusters (Beta).

Resolution

To resolve this issue, use the 10.220.0.0/16 subnet as Kubernetes Service Network CIDR.