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.

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(guide): fix not being able to link to migration steps heading because of duplication #1903

Merged
merged 2 commits into from
Sep 18, 2024
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions app/_src/guides/migration-to-the-new-policies.md
Original file line number Diff line number Diff line change
Expand Up @@ -201,7 +201,7 @@ spec:
threshold: 36' | kubectl apply -f-
```

## Migration to the new policies
## Migration steps

It's time to migrate the demo app to the new policies.

Expand All @@ -211,7 +211,7 @@ It's possible to migrate all policies at once, but small portions are preferable

The generalized migration process roughly consists of 4 steps:

1. Create a new [targetRef](/docs/{{ page.version }}/policies/targetref) policy as a replacement for exising [source/destination](/docs/{{ page.version }}/policies/general-notes-about-kuma-policies/) policy.
1. Create a new [targetRef](/docs/{{ page.version }}/policies/targetref) policy as a replacement for exising [source/destination](/docs/{{ page.version }}/policies/general-notes-about-kuma-policies/) policy (do not forget about default policies that might not be stored in your source control).
The corresponding new policy type can be found in [the table](/docs/{{ page.version }}/policies/introduction).
Deploy the policy in [shadow mode](/docs/{{ page.version }}/policies/applying-policies/#applying-policies-in-shadow-mode) to avoid any traffic disruptions.
2. Using Inspect API review the list of changes that are going to be created by the new policy.
Expand Down
Loading