Skip to content

[v2-9] docs: fix two broken in-page anchors (AWS integration, Helm use case) #2679

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

Merged
matheuscscp merged 1 commit into from
Oct 9, 2026
Merged

[v2-9] docs: fix two broken in-page anchors (AWS integration, Helm use case) #2679

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
docs: fix two broken in-page anchors 
- integrations/aws.md links to #for-eks-pod-identity, but the section
  is titled "With EKS Pod Identity" (#with-eks-pod-identity).
- use-cases/helm.md links to the "Refer to values in ConfigMaps
  generated with Kustomize" section of the Helm guide, which was
  replaced by "Reacting immediately to changes in referenced Secrets
  and ConfigMaps" in df52250.

Signed-off-by: Satvik Mishra <Satvikmishra.ipu146183@maims.ac.in>
(cherry picked from commit 6ec09d4)
  • Loading branch information
@SatvikMishra08 @github-actions
SatvikMishra08 authored and github-actions[bot] committed Oct 9, 2026
commit d4c21f2a407c6f4529a6cdbb830b399238c0fd4e
2 changes: 1 addition & 1 deletion content/en/flux/integrations/aws.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,7 +232,7 @@ to the IAM Role.

Trust policies are similar in syntax to permission policies, but for each
of these two features the trust policy JSON document has particular requirements.
For EKS Pod Identity, see [here](#for-eks-pod-identity). For OIDC Federation, see
For EKS Pod Identity, see [here](#with-eks-pod-identity). For OIDC Federation, see
[here](#supported-identity-types).

To create an IAM Role with a trust policy using ACK, you can use the following custom resource
Expand Down
2 changes: 1 addition & 1 deletion content/en/flux/use-cases/helm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ You may manage these `ConfigMap` and `Secret` resources any way you wish,
but there are several benefits to managing these with the Flux Kustomize Controller.

It is fairly straightforward to use Kustomize `configMapGenerator`
to [trigger a Helm release upgrade every time the encoded values change](../guides/helmreleases.md#refer-to-values-in-configmaps-generated-with-kustomize).
to [trigger a Helm release upgrade every time the encoded values change](../guides/helmreleases.md#reacting-immediately-to-changes-in-referenced-secrets-and-configmaps).
This common use case currently solveable in Helm
by [adding specially crafted annotations](https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments)
to a chart. The Flux Kustomize Controller method allows you to accomplish this
Expand Down
Loading