Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📖 Fix broken book links #7436

Merged
merged 1 commit into from
Oct 20, 2022
Merged

📖 Fix broken book links #7436

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/book/src/security/pod-security-standards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ It is using ClusterClass variables and patches to inject the configuration.

## Adding a basic Pod Security Standards configuration to a ClusterClass

By adding the following variables and patches Pod Security Standards can be added to every ClusterClass which references a [Kubeadm based control plane](../tasks/kubeadm-control-plane.md).
By adding the following variables and patches Pod Security Standards can be added to every ClusterClass which references a [Kubeadm based control plane](../tasks/control-plane/kubeadm-control-plane.md).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to figure out why this didn't happen on the main version of the PR - but having the weekly job is a nice 'eventually correct' feature for the main version of the book.


### Adding the variables to a ClusterClass

Expand Down
2 changes: 1 addition & 1 deletion docs/book/src/tasks/control-plane/kubeadm-control-plane.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,4 +38,4 @@ Cluster API Machines:
for additional details.

<!-- links -->
[upgrades]: upgrading-clusters.md#how-to-upgrade-the-kubernetes-control-plane-version
[upgrades]: ../upgrading-clusters.md#how-to-upgrade-the-kubernetes-control-plane-version
2 changes: 1 addition & 1 deletion docs/book/src/tasks/updating-machine-templates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ field and the controller would orchestrate the upgrade by managing `MachineSets`
In all cases, the `name` field should be updated to point to the newly-modified
infrastructure machine template. This will trigger a rolling update. (This same process
is described in the documentation for [upgrading the underlying machine image for
KubeadmControlPlane](./kubeadm-control-plane.md) in the "How to upgrade the underlying
KubeadmControlPlane](./control-plane/kubeadm-control-plane.md) in the "How to upgrade the underlying
machine image" section.)

Some infrastructure providers _may_, at their discretion, choose to support in-place
Expand Down