Skip to content

Commit 86264ea

Browse files
committed
use use IPv6 Address Prefix Reserved for Documentation
1 parent bad7e81 commit 86264ea

File tree

3 files changed

+14
-14
lines changed

3 files changed

+14
-14
lines changed

content/en/docs/concepts/services-networking/dns-pod-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -308,7 +308,7 @@ kubectl exec -it dns-example -- cat /etc/resolv.conf
308308
```
309309
The output is similar to this:
310310
```
311-
nameserver fd00:79:30::a
311+
nameserver 2001:db8:30::a
312312
search default.svc.cluster-domain.example svc.cluster-domain.example cluster-domain.example
313313
options ndots:5
314314
```

content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ on the provisioned node, specify the `--cri-socket` argument to `kubeadm`. See
122122
with the default gateway to set the advertise address for this particular control-plane node's API server.
123123
To use a different network interface, specify the `--apiserver-advertise-address=<ip-address>` argument
124124
to `kubeadm init`. To deploy an IPv6 Kubernetes cluster using IPv6 addressing, you
125-
must specify an IPv6 address, for example `--apiserver-advertise-address=fd00::101`
125+
must specify an IPv6 address, for example `--apiserver-advertise-address=2001:db8::101`
126126

127127
To initialize the control-plane node run:
128128

@@ -377,7 +377,7 @@ The output is similar to:
377377
```
378378

379379
{{< note >}}
380-
To specify an IPv6 tuple for `<control-plane-host>:<control-plane-port>`, IPv6 address must be enclosed in square brackets, for example: `[fd00::101]:2073`.
380+
To specify an IPv6 tuple for `<control-plane-host>:<control-plane-port>`, IPv6 address must be enclosed in square brackets, for example: `[2001:db8::101]:2073`.
381381
{{< /note >}}
382382

383383
The output should look something like:

content/en/docs/tasks/network/validate-dual-stack.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ kubectl get nodes k8s-linuxpool1-34450317-0 -o go-template --template='{{range .
3939
```
4040
```
4141
10.244.1.0/24
42-
a00:100::/24
42+
2001:db8::/64
4343
```
4444
There should be one IPv4 block and one IPv6 block allocated.
4545

@@ -50,8 +50,8 @@ kubectl get nodes k8s-linuxpool1-34450317-0 -o go-template --template='{{range .
5050
```
5151
```
5252
Hostname: k8s-linuxpool1-34450317-0
53-
InternalIP: 10.240.0.5
54-
InternalIP: 2001:1234:5678:9abc::5
53+
InternalIP: 10.0.0.5
54+
InternalIP: 2001:db8:10::5
5555
```
5656

5757
### Validate Pod addressing
@@ -63,7 +63,7 @@ kubectl get pods pod01 -o go-template --template='{{range .status.podIPs}}{{prin
6363
```
6464
```
6565
10.244.1.4
66-
a00:100::4
66+
2001:db8::4
6767
```
6868

6969
You can also validate Pod IPs using the Downward API via the `status.podIPs` fieldPath. The following snippet demonstrates how you can expose the Pod IPs via an environment variable called `MY_POD_IPS` within a container.
@@ -82,7 +82,7 @@ The following command prints the value of the `MY_POD_IPS` environment variable
8282
kubectl exec -it pod01 -- set | grep MY_POD_IPS
8383
```
8484
```
85-
MY_POD_IPS=10.244.1.4,a00:100::4
85+
MY_POD_IPS=10.244.1.4,2001:db8::4
8686
```
8787

8888
The Pod's IP addresses will also be written to `/etc/hosts` within a container. The following command executes a cat on `/etc/hosts` on a dual stack Pod. From the output you can verify both the IPv4 and IPv6 IP address for the Pod.
@@ -99,7 +99,7 @@ fe00::0 ip6-mcastprefix
9999
fe00::1 ip6-allnodes
100100
fe00::2 ip6-allrouters
101101
10.244.1.4 pod01
102-
a00:100::4 pod01
102+
2001:db8::4 pod01
103103
```
104104

105105
## Validate Services
@@ -161,9 +161,9 @@ metadata:
161161
app.kubernetes.io/name: MyApp
162162
name: my-service
163163
spec:
164-
clusterIP: fd00::5118
164+
clusterIP: 2001:db8:fd00::5118
165165
clusterIPs:
166-
- fd00::5118
166+
- 2001:db8:fd00::5118
167167
ipFamilies:
168168
- IPv6
169169
ipFamilyPolicy: SingleStack
@@ -210,7 +210,7 @@ Type: ClusterIP
210210
IP Family Policy: PreferDualStack
211211
IP Families: IPv4,IPv6
212212
IP: 10.0.216.242
213-
IPs: 10.0.216.242,fd00::af55
213+
IPs: 10.0.216.242,2001:db8:fd00::af55
214214
Port: <unset> 80/TCP
215215
TargetPort: 9376/TCP
216216
Endpoints: <none>
@@ -233,8 +233,8 @@ kubectl get svc -l app.kubernetes.io/name=MyApp
233233
Validate that the Service receives a `CLUSTER-IP` address from the IPv6 address block along with an `EXTERNAL-IP`. You may then validate access to the service via the IP and port.
234234

235235
```shell
236-
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
237-
my-service LoadBalancer fd00::7ebc 2603:1030:805::5 80:30790/TCP 35s
236+
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
237+
my-service LoadBalancer 2001:db8:fd00::7ebc 2603:1030:805::5 80:30790/TCP 35s
238238
```
239239

240240

0 commit comments

Comments
 (0)