Merge pull request #22968 from blueabysm/fix-links-which-pointed-to-unavailable-location
Fix links which pointed to unavailable location
This commit is contained in:
commit
6005510284
|
@ -23,7 +23,7 @@ To keep kubeadm lean, focused, and vendor/infrastructure agnostic, the following
|
|||
- Non-critical add-ons, e.g. for monitoring, logging, and visualization
|
||||
- Specific cloud provider integrations
|
||||
|
||||
Infrastructure provisioning, for example, is left to other SIG Cluster Lifecycle projects, such as the [Cluster API](https://github.com/kubernetes-sigs/cluster-api). Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the [control plane](/docs/concepts/#kubernetes-control-plane). The user may install their preferred networking solution and other add-ons on top of Kubernetes *after* cluster creation.
|
||||
Infrastructure provisioning, for example, is left to other SIG Cluster Lifecycle projects, such as the [Cluster API](https://github.com/kubernetes-sigs/cluster-api). Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the [control plane](/docs/concepts/overview/components/#control-plane-components). The user may install their preferred networking solution and other add-ons on top of Kubernetes *after* cluster creation.
|
||||
|
||||
### What kubeadm's GA release means
|
||||
|
||||
|
|
|
@ -43,7 +43,7 @@ Those tasks are addressed by other SIG Cluster Lifecycle projects, such as the
|
|||
[Cluster API](https://github.com/kubernetes-sigs/cluster-api) for infrastructure provisioning and management.
|
||||
|
||||
Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the
|
||||
[control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane).
|
||||
[control plane](/docs/concepts/overview/components/#control-plane-components).
|
||||
|
||||

|
||||
|
||||
|
|
|
@ -154,8 +154,8 @@ controller does.
|
|||
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
||||
* Read about the [Kubernetes control plane](/docs/concepts/#kubernetes-control-plane)
|
||||
* Discover some of the basic [Kubernetes objects](/docs/concepts/#kubernetes-objects)
|
||||
* Read about the [Kubernetes control plane](/docs/concepts/overview/components/)
|
||||
* Discover some of the basic [Kubernetes objects](/docs/concepts/overview/working-with-objects)
|
||||
* Learn more about the [Kubernetes API](/docs/concepts/overview/kubernetes-api/)
|
||||
* If you want to write your own controller, see [Extension Patterns](/docs/concepts/extend-kubernetes/extend-cluster/#extension-patterns) in Extending Kubernetes.
|
||||
|
||||
|
|
|
@ -9,7 +9,7 @@ weight: 30
|
|||
Operators are software extensions to Kubernetes that make use of
|
||||
[custom resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
|
||||
to manage applications and their components. Operators follow
|
||||
Kubernetes principles, notably the [control loop](/docs/concepts/#kubernetes-control-plane).
|
||||
Kubernetes principles, notably the [control loop](/docs/concepts/architecture/controller).
|
||||
|
||||
<!-- body -->
|
||||
|
||||
|
|
Loading…
Reference in New Issue