Skip to content

Commit

Permalink
Updates per review
Browse files Browse the repository at this point in the history
Signed-off-by: Bridget Kromhout <[email protected]>
  • Loading branch information
bridgetkromhout committed Nov 22, 2021
1 parent d5dbdb1 commit 0976334
Showing 1 changed file with 8 additions and 3 deletions.
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: blog
title: 'Kubernetes 1.23: Dual-stack IPv4/IPv6 Networking Reaches GA'
date: 2021-12-07
date: 2021-12-08
slug: dual-stack-networking-ga
---

Expand All @@ -24,9 +24,14 @@ The Service API now has new fields to support dual-stack, replacing the single i

## Default behavior remains single-stack

Starting in 1.20, the underlying networking for Kubernetes has included dual-stack whether or not a cluster was configured with the feature flag to enable dual-stack. Now that the feature is stable in 1.23, the feature flag is removed.

However, Pods and Services default to single-stack unless `ipFamilyPolicy` specifies PreferDualStack or RequireDualStack. Even though dual-stack is possible, it is not mandatory to use it. Examples in the documentation show the variety possible in [dual-stack service configuration](/docs/concepts/services-networking/dual-stack/#dual-stack-service-configuration-scenarios).
Starting in 1.20 with the re-implementation of dual-stack services as alpha, the underlying networking for Kubernetes has included dual-stack whether or not a cluster was configured with the feature flag to enable dual-stack.

Kubernetes 1.23 removed that feature flag as part of graduating the feature to stable. Dual-stack networking is always available if you want to configure it. You can set your cluster network to operate as single-stack IPv4, as single-stack IPv6, or as dual-stack IPv4/IPv6.

Pods and Services default to whatever the CNI plugin sets. If your CNI plugin assigns single-stack IPs, you will have single-stack unless `ipFamilyPolicy` specifies PreferDualStack or RequireDualStack. If your CNI plugin assigns dual-stack IPs, `pod.status.PodIPs` defaults to dual-stack.

Even though dual-stack is possible, it is not mandatory to use it. Examples in the documentation show the variety possible in [dual-stack service configuration](/docs/concepts/services-networking/dual-stack/#dual-stack-service-configuration-scenarios).


## Try dual-stack right now
Expand Down

0 comments on commit 0976334

Please sign in to comment.