Skip to content

Commit 383ddf9

Browse files
author
Kate Osborn
committed
Change example policy names
1 parent 5af1dec commit 383ddf9

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

site/content/overview/custom-policies.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -61,14 +61,14 @@ The following diagram shows how Inherited Policies work in NGINX Gateway Fabric
6161

6262
There are three policies defined:
6363

64-
- Blue policy that targets the `dev` Gateway
65-
- Orange policy that targets the `baz` HTTPRoute
66-
- Pink policy that targets the `foo` HTTPRoute
67-
68-
The settings in the blue policy affect the `dev` Gateway and are inherited by all the HTTPRoutes attached to `dev`.
69-
The orange and pink policies are attached to the `baz` and `foo` HTTPRoutes. Since HTTPRoutes are lower than Gateways in the hierarchy, the settings defined in the orange and pink policies override those in the blue policy.
70-
Since the pink policy only defines the `retries` setting, it still inherits the `timeout` setting from the blue policy.
71-
The `bar` HTTPRoute has no policy attached to it and inherits all the settings from the blue policy.
64+
- `dev-policy` that targets the `dev` Gateway
65+
- `baz-policy` that targets the `baz` HTTPRoute
66+
- `foo-policy` that targets the `foo` HTTPRoute
67+
68+
The settings in `dev-policy` affect the `dev` Gateway and are inherited by all the HTTPRoutes attached to `dev`.
69+
The `baz-policy` and `foo-policy` are attached to the `baz` and `foo` HTTPRoutes. Since HTTPRoutes are lower than Gateways in the hierarchy, the settings defined in them override those in the `dev` policy.
70+
Since the `foo-policy` only defines the `retries` setting, it still inherits the `timeout` setting from `dev-policy`.
71+
The `bar` HTTPRoute has no policy attached to it and inherits all the settings from `dev-policy`.
7272

7373
## Merging Policies
7474

8.54 KB
Loading

0 commit comments

Comments
 (0)