Fix remaining issues from report

* https://github.com/kingdonb/link-checker-gpt/actions/runs/5870914877 Test here showed these issues standing in the way of a green checkmark There are still a few more fixes through: * fluxcd/source-controller#1200 Signed-off-by: Kingdon Barrett <[email protected]>
fluxcd · Aug 15, 2023 · dc2c383 · dc2c383
1 parent 4477178
commit dc2c383
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/content/en/flux/guides/image-update.md b/content/en/flux/guides/image-update.md
@@ -65,7 +65,7 @@ If you bootstrapped Flux before, you need to add
 `--components-extra=image-reflector-controller,image-automation-controller` to your
 bootstrapping routine as image automation components are not installed by default.
 Please note that you need to delete the `flux-system` secret before rerunning bootstrap
-to [rotate the deploy key](/flux/installation/#deploy-key-rotation).
+to [rotate the deploy key](/flux/installation/configuration/deploy-key-rotation/).
 {{% /alert %}}
 
 Install Flux with the image automation components:

diff --git a/content/en/flux/guides/mozilla-sops.md b/content/en/flux/guides/mozilla-sops.md
@@ -311,7 +311,7 @@ kubectl -n flux-system rollout restart deployment/kustomize-controller
 ```
 
 {{% alert color="info" title="Bootstrap" %}}
-Note that when using `flux bootstrap` you can [set the annotation](/flux/cheatsheets/bootstrap/#iam-roles-for-service-accounts/) to take effect at install time.
+Note that when using `flux bootstrap` you can [set the annotation](/flux/cheatsheets/bootstrap/#iam-roles-for-service-accounts) to take effect at install time.
 {{% /alert %}}
 
 #### Azure

diff --git a/content/en/flux/migration/helm-operator-migration.md b/content/en/flux/migration/helm-operator-migration.md
@@ -271,7 +271,7 @@ spec:
     path: ./charts/my-chart
 ```
 
-With the Helm Controller, you create a `GitRepository` resource in addition to the `HelmRelease` you would normally create (for all available fields, consult the [Source API reference](/flux/components/source/api/#source.toolkit.fluxcd.io/v1.GitRepository):
+With the Helm Controller, you create a `GitRepository` resource in addition to the `HelmRelease` you would normally create (for all available fields, consult the [Source API reference](/flux/components/source/api/v1/#source.toolkit.fluxcd.io/v1.GitRepository):
 
 ```yaml
 ---

diff --git a/content/en/flux/security/secrets-management.md b/content/en/flux/security/secrets-management.md
@@ -92,7 +92,7 @@ could impact your solution.
 Flux supports the two main names in Encrypted Secrets and has specific how-to guides for them:
 
 - [Mozilla SOPS Guide](/flux/guides/mozilla-sops/)
-- [Secrets decryption](/flux/components/kustomize/kustomization/#secrets-decryption)
+- [Secrets decryption](/flux/components/kustomize/kustomization/#decryption)
 
 #### Secrets Synchronized by Operators
-Original file line number
+Diff line change
@@ Expand Up / @@ -271,7 +271,7 @@ spec: @@
         path: ./charts/my-chart
     ```
-    With the Helm Controller, you create a `GitRepository` resource in addition to the `HelmRelease` you would normally create (for all available fields, consult the [Source API reference](/flux/components/source/api/#source.toolkit.fluxcd.io/v1.GitRepository):
+    With the Helm Controller, you create a `GitRepository` resource in addition to the `HelmRelease` you would normally create (for all available fields, consult the [Source API reference](/flux/components/source/api/v1/#source.toolkit.fluxcd.io/v1.GitRepository):
     ```yaml
     ---
@@ Expand Down @@