Skip to content

Commit a168843

Browse files
author
Cecile Robert-Michon
committed
fix dead links
1 parent 1d39ee1 commit a168843

File tree

8 files changed

+14
-14
lines changed

8 files changed

+14
-14
lines changed

docs/book/src/clusterctl/provider-contract.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ While defining the Deployment Spec, the container that executes the controller b
135135

136136
The manager MUST support a `--namespace` flag for specifying the namespace where the controller
137137
will look for objects to reconcile; however, clusterctl will always install providers watching for all namespaces
138-
(`--namespace=""`); for more details see [support for multiple instances](../../developer/architecture/controllers/support-multiple-instances.md)
138+
(`--namespace=""`); for more details see [support for multiple instances](../developer/architecture/controllers/support-multiple-instances.md)
139139
for more context.
140140

141141
#### Variables

docs/book/src/developer/e2e.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ defined in the [Cluster API test framework] to check if the operation completed
145145

146146
### Naming the test spec
147147

148-
You can categorize the test with a custom label that can be used to filter a category of E2E tests to be run. Currently, the cluster-api codebase has [these labels](./testing.html#running-specific-tests) which are used to run a focused subset of tests.
148+
You can categorize the test with a custom label that can be used to filter a category of E2E tests to be run. Currently, the cluster-api codebase has [these labels](./testing.md#running-specific-tests) which are used to run a focused subset of tests.
149149

150150
## Tear down
151151

docs/book/src/developer/providers/implementers-guide/generate_crds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ make manifests
7676
```
7777
7878
[status]: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#status-subresource
79-
[rbac]: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16/#customresourcesubresources-v1beta1-apiextensions-k8s-io
79+
[rbac]: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.22/#customresourcesubresources-v1beta1-apiextensions-k8s-io
8080
[kbstatus]: https://book.kubebuilder.io/reference/generating-crd.html?highlight=status#status
8181
8282
### Apply further customizations

docs/book/src/tasks/experimental-features/cluster-classes.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The ClusterClass - first in the yaml below - contains references to the template
6161
* DockerMachineTemplate
6262
* KubeadmConfigTemplate
6363

64-
The full ClusterClass definition can also be found in the [CAPI repo](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/yamls/clusterclass.yaml).
64+
The full ClusterClass definition can also be found in the [CAPI repo](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/experimental-features/yamls/clusterclass.yaml).
6565

6666
<details><summary>ClusterClass</summary>
6767

@@ -75,14 +75,14 @@ The full ClusterClass definition can also be found in the [CAPI repo](https://ra
7575
To create the objects on your local cluster run:
7676

7777
```bash
78-
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/yamls/clusterclass.yaml
78+
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/experimental-features/yamls/clusterclass.yaml
7979
```
8080

8181
#### Enable networking for workload clusters
8282

8383
To make sure workload clusters come up with a functioning network a Kindnet ConfigMap with a Kindnet ClusterResourceSet is required. Kindnet only offers networking for Clusters built with Kind and CAPD. This can be substituted for any other networking solution for Kubernetes e.g. Calico as used in the Quickstart guide.
8484

85-
The kindnet configuration file can be found in the [CAPI repo](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/yamls/clusterclass.yaml).
85+
The kindnet configuration file can be found in the [CAPI repo](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/experimental-features/yamls/clusterclass.yaml).
8686

8787
To create the resources run:
8888
```bash
@@ -100,10 +100,10 @@ This is a Cluster definition that leverages the ClusterClass created above to de
100100
```
101101
</details>
102102

103-
Create the Cluster object from the file in [the CAPI repo](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/yamls/clusterclass-quickstart.yaml) with:
103+
Create the Cluster object from the file in [the CAPI repo](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/experimental-features/yamls/clusterclass-quickstart.yaml) with:
104104

105105
```bash
106-
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/yamls/clusterclass-quickstart.yaml
106+
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/book/src/tasks/experimental-features/yamls/clusterclass-quickstart.yaml
107107
```
108108

109109
#### Verify the workload cluster is running

docs/proposals/20191017-kubeadm-based-control-plane.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,8 +128,8 @@ Non-Goals listed in this document are intended to scope bound the current v1alph
128128
- To manage etcd clusters in any topology other than stacked etcd (externally managed etcd clusters can still be leveraged).
129129
- To address disaster recovery constraints, e.g. restoring a control plane from 0 replicas using a filesystem or volume snapshot copy of data persisted in etcd.
130130
- To support rollbacks, as there is no data store rollback guarantee for Kubernetes. Consumers should perform backups of the cluster prior to performing potentially destructive operations.
131-
- To mutate the configuration of live, running clusters (e.g. changing api-server flags), as this is the responsibility of the [component configuration working group](https://git.k8s.io/community/wg-component-standard).
132-
- To provide configuration of external cloud providers (i.e. the [cloud-controller-manager](https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/)).This is deferred to kubeadm.
131+
- To mutate the configuration of live, running clusters (e.g. changing api-server flags), as this is the responsibility of the [component configuration working group](https://github.com/orgs/kubernetes/projects/26).
132+
- To provide configuration of external cloud providers (i.e. the [cloud-controller-manager](https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/)). This is deferred to kubeadm.
133133
- To provide CNI configuration. This is deferred to external, higher level tooling.
134134
- To provide the upgrade logic to handle changes to infrastructure (networks, firewalls etc…) that may need to be done to support a control plane on a newer version of Kubernetes (e.g. a cloud controller manager requires updated permissions against infrastructure APIs). We expect the work on [add-on components](https://git.k8s.io/community/sig-cluster-lifecycle#cluster-addons) to help to resolve some of these issues.
135135
- To provide automation around the horizontal or vertical scaling of control plane components, especially as etcd places hard performance limits beyond 3 nodes (due to latency).

docs/proposals/20200804-windows-support.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ There is prior art for building Windows base images. For example, AKS-Engine has
118118
Another example is the the [sig-windows-tools](https://github.com/kubernetes-sigs/sig-windows-tools) which provide scripts for image configuration when using Kubeadm.
119119

120120
Although the Linux implementation in image-builder uses Ansible for configuration, Windows isn't going to share
121-
the same configuration because [Ansible](https://docs.ansible.com/ansible/latest/user_guide/windows.html) requires [Windows specific modules](https://docs.ansible.com/ansible/latest/modules/list_of_windows_modules.html) to do the configuration.
121+
the same configuration because [Ansible](https://docs.ansible.com/ansible/latest/user_guide/windows.html) requires [Windows specific modules](https://docs.ansible.com/ansible/2.9/modules/list_of_windows_modules.html) to do the configuration.
122122

123123
#### Kubelet and other component configuration
124124

@@ -144,7 +144,7 @@ The conclusion of the [issue](https://github.com/kubernetes-sigs/cluster-api/iss
144144

145145
By leveraging cloudbase-init, an infrastructure provider implementation will require only a few changes which include:
146146

147-
- Make changes to their provider api to enable Windows OS infra machines ([example](https://github.com/ionutbalutoiu/cluster-api-provider-azure/commit/9c8daedac75959b141fec7ea909c2c1fd0bd484b))
147+
- Make changes to their provider api to enable Windows OS infra machines ([example](https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/1036/commits/e753a32fccdf6b825b606f12bb1acd6e34a70339#diff-492149096931cdfde8cf61676230879e41cfdb1afeb74784cdf85bca2272a1be))
148148
- Ensuring cloudbase-init is configured properly to read UserData which will contain the cloud-init script. Users must configure
149149
[cloudbase-init with a metadata service](https://cloudbase-init.readthedocs.io/en/latest/services.html#configuring-available-services) that has support for [UserData](https://cloudbase-init.readthedocs.io/en/latest/userdata.html) ([example](https://cloudbase-init.readthedocs.io/en/latest/tutorial.html#configuration-file)).
150150

docs/proposals/YYYYMMDD-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To get started with this template:
2929
Aim for single topic PRs to keep discussions focused.
3030
If you disagree with what is already in a document, open a new PR with suggested changes.
3131

32-
The canonical place for the latest set of instructions (and the likely source of this file) is [here](/docs/proposals/YYYYMMDD-template.md).
32+
The canonical place for the latest set of instructions (and the likely source of this file) is [here](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/docs/proposals/YYYYMMDD-template.md).
3333

3434
The `Metadata` section above is intended to support the creation of tooling around the proposal process.
3535
This will be a YAML section that is fenced as a code block.

test/infrastructure/docker/exp/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ In short, code in this subrepository is not subject to any compatibility or depr
88

99
Experiments follow a strict lifecycle: Alpha -> Beta prior to Graduation.
1010

11-
For more information on graduation criteria, see: [Contributing Guidelines](../CONTRIBUTING.md#experiments)
11+
For more information on graduation criteria, see: [Contributing Guidelines](../../../../CONTRIBUTING.md#experiments)
1212

1313
## Active Features
1414
DockerMachinePool (alpha)

0 commit comments

Comments
 (0)