-
Notifications
You must be signed in to change notification settings - Fork 522
feat: allow creation of dualstack Windows clusters #4176
Conversation
Summarizing 5 Failures: [Fail] Azure Container Cluster using the Kubernetes Orchestrator regardless of agent pool type [It] should have functional container networking DNS [Fail] Azure Container Cluster using the Kubernetes Orchestrator with a windows agent pool [It] should be able to deploy and scale an iis webserver [Fail] Azure Container Cluster using the Kubernetes Orchestrator with a windows agent pool [It] should be able to resolve DNS across windows and linux deployments [Fail] Azure Container Cluster using the Kubernetes Orchestrator with a windows agent pool [It] should expect containers to be recreated after node restart [Fail] Azure Container Cluster using the Kubernetes Orchestrator with a windows agent pool [It] should be able to rotate docker logs |
/azp run pr-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov Report
@@ Coverage Diff @@
## master #4176 +/- ##
==========================================
- Coverage 72.06% 72.04% -0.03%
==========================================
Files 141 141
Lines 21686 21636 -50
==========================================
- Hits 15628 15587 -41
+ Misses 5107 5099 -8
+ Partials 951 950 -1
Continue to review full report at Codecov.
|
Co-authored-by: James Sturtevant <jsturtevant@gmail.com>
Do you have a handle on why the tests are failing and what is needed to pass? Have you tried this with Containerd? |
I haven't dug into it, it looks like something to do with azurecni, pods are not able to come up and I see "No available addresses". However, these tests pass when I run them in isolation, so a mix of some of these tests are not working. In addition, I didn't notice any issues while running our workloads, in similar dual stack clusters. And, no I haven't tested this with containerd. |
@jsturtevant, looks like the tests were failing because there was an issue with azure cni (Azure/azure-container-networking#760) which was fixed recently (Azure/azure-container-networking#755) and updated in aks-engine (#4183). With the latest aks-engine all the e2e tests pass with both docker and containerd runtimes. |
/azp run pr-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run pr-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
…enk/allowWinDualStack
/azp run pr-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run pr-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/lgtm this will require an update to the provisioning scripts: https://github.com/Azure/aks-engine/blob/master/docs/topics/windows-provisioning-scripts.md @aramase could you give a look on more look from ipv6 perspective? |
@@ -15,6 +15,7 @@ $global:NetworkMode = "L2Bridge" | |||
$global:NetworkPlugin = $Global:ClusterConfiguration.Cni.Name | |||
$global:ContainerRuntime = $Global:ClusterConfiguration.Cri.Name | |||
$UseContainerD = ($global:ContainerRuntime -eq "containerd") | |||
$IsDualStackEnabled = $Global:ClusterConfiguration.Kubernetes.Kubeproxy.FeatureGates -contains "IPv6DualStack=true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker for this PR but we should also think about how we would do this in v1.21+
. Dual-stack is beta as of v1.21
and these feature gates are enabled by default. So they will not be explicitly set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aramase, jsturtevant, vavenk-ms The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Reason for Change:
Allow creation of dual stack Windows Kubernetes clusters. This was restricted as Windows did not support dual stack. From Windows version 2004 (10.0.19041.610) and Kubernetes version 1.19, dual stack is supported. https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#ipv4-ipv6-dual-stack
Issue Fixed:
#4171
Credit Where Due:
Does this change contain code from or inspired by another project?
If "Yes," did you notify that project's maintainers and provide attribution?
Requirements:
Notes: