Skip to content

Commit b16e2bc

Browse files
committed
Replace Go Doc URL with pkg.go.dev
1 parent f71cba2 commit b16e2bc

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

content/en/docs/setup/best-practices/certificates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ Required certificates:
9191
the load balancer stable IP and/or DNS name, `kubernetes`, `kubernetes.default`, `kubernetes.default.svc`,
9292
`kubernetes.default.svc.cluster`, `kubernetes.default.svc.cluster.local`)
9393

94-
where `kind` maps to one or more of the [x509 key usage](https://godoc.org/k8s.io/api/certificates/v1beta1#KeyUsage) types:
94+
where `kind` maps to one or more of the [x509 key usage](https://pkg.go.dev/k8s.io/api/certificates/v1beta1#KeyUsage) types:
9595

9696
| kind | Key usage |
9797
|--------|---------------------------------------------------------------------------------|

content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ The built-in signer is part of [`kube-controller-manager`](/docs/reference/comma
173173

174174
To activate the built-in signer, you must pass the `--cluster-signing-cert-file` and `--cluster-signing-key-file` flags.
175175

176-
If you're creating a new cluster, you can use a kubeadm [configuration file](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3):
176+
If you're creating a new cluster, you can use a kubeadm [configuration file](https://pkg.go.dev/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3):
177177

178178
```yaml
179179
apiVersion: kubeadm.k8s.io/v1beta3

content/en/docs/tasks/tls/managing-tls-in-a-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ some extra application configuration. You will need to add the CA certificate
4747
bundle to the list of CA certificates that the TLS client or server trusts. For
4848
example, you would do this with a golang TLS config by parsing the certificate
4949
chain and adding the parsed certificates to the `RootCAs` field in the
50-
[`tls.Config`](https://godoc.org/crypto/tls#Config) struct.
50+
[`tls.Config`](https://pkg.go.dev/crypto/tls#Config) struct.
5151

5252
{{< note >}}
5353
Even though the custom CA certificate may be included in the filesystem (in the

0 commit comments

Comments
 (0)