Skip to content

DOCS-3098: Fix inaccuracies on the Tier reference #3120

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
ctauchen merged 4 commits into from
Oct 19, 2026
Merged

DOCS-3098: Fix inaccuracies on the Tier reference #3120

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f0d3e18
Fix tier order default and built-in tier text (next)
ctauchen Oct 16, 2026
cb436d5
Fix tier order default and built-in tier text (3.33)
ctauchen Oct 16, 2026
35aafcf
Fix tier order default and built-in tier text (3.32)
ctauchen Oct 16, 2026
3248a93
Fix tier order default and built-in tier text (3.31)
ctauchen Oct 16, 2026
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 calico/reference/resources/tier.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ spec:

| Field | Description | Accepted Values | Schema | Default |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------ | --------------- | ------ | --------------------- |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value indicates highest order (lowest precedence) | | float | `nil` (highest order) |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value is treated as order `1000000`, the order of the `default` Tier | | float | `1000000` |
| defaultAction | (Optional) Indicates the default action, when this Tier applies to an endpoint, but takes no action on the packet | `Deny`, `Pass` | string | `Deny` |

All Policies created by $[prodname] orchestrator integrations are created in the default (last) Tier.
All Policies created by $[prodname] orchestrator integrations are created in the `default` Tier (order `1000000`), except Kubernetes ClusterNetworkPolicies, which are created in the `kube-admin` (order `1000`) and `kube-baseline` (order `10000000`) Tiers. If you install $[prodname] with the operator and the `projectcalico.org/v3` API is available (through the $[prodname] API server or v3 CRDs), the operator also creates a `calico-system` Tier (order `100`) for the policies it installs to allow $[prodname] component traffic.
4 changes: 2 additions & 2 deletions calico_versioned_docs/version-3.31/reference/resources/tier.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ spec:

| Field | Description | Accepted Values | Schema | Default |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------ | --------------- | ------ | --------------------- |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value indicates highest order (lowest precedence) | | float | `nil` (highest order) |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value is treated as order `1000000`, the order of the `default` Tier | | float | `1000000` |
| defaultAction | (Optional) Indicates the default action, when this Tier applies to an endpoint, but takes no action on the packet | `Deny`, `Pass` | string | `Deny` |

All Policies created by $[prodname] orchestrator integrations are created in the default (last) Tier.
All Policies created by $[prodname] orchestrator integrations are created in the `default` Tier (order `1000000`), except Kubernetes AdminNetworkPolicies and BaselineAdminNetworkPolicies, which are created in the `adminnetworkpolicy` (order `1000`) and `baselineadminnetworkpolicy` (order `10000000`) Tiers.
4 changes: 2 additions & 2 deletions calico_versioned_docs/version-3.32/reference/resources/tier.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ spec:

| Field | Description | Accepted Values | Schema | Default |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------ | --------------- | ------ | --------------------- |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value indicates highest order (lowest precedence) | | float | `nil` (highest order) |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value is treated as order `1000000`, the order of the `default` Tier | | float | `1000000` |
| defaultAction | (Optional) Indicates the default action, when this Tier applies to an endpoint, but takes no action on the packet | `Deny`, `Pass` | string | `Deny` |

All Policies created by $[prodname] orchestrator integrations are created in the default (last) Tier.
All Policies created by $[prodname] orchestrator integrations are created in the `default` Tier (order `1000000`), except Kubernetes ClusterNetworkPolicies, which are created in the `kube-admin` (order `1000`) and `kube-baseline` (order `10000000`) Tiers. If you install $[prodname] with the operator and the `projectcalico.org/v3` API is available (through the $[prodname] API server or v3 CRDs), the operator also creates a `calico-system` Tier (order `100`) for the policies it installs to allow $[prodname] component traffic.
4 changes: 2 additions & 2 deletions calico_versioned_docs/version-3.33/reference/resources/tier.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ spec:

| Field | Description | Accepted Values | Schema | Default |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------ | --------------- | ------ | --------------------- |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value indicates highest order (lowest precedence) | | float | `nil` (highest order) |
| order | (Optional) Indicates priority of this Tier, with lower order taking precedence. No value is treated as order `1000000`, the order of the `default` Tier | | float | `1000000` |
| defaultAction | (Optional) Indicates the default action, when this Tier applies to an endpoint, but takes no action on the packet | `Deny`, `Pass` | string | `Deny` |

All Policies created by $[prodname] orchestrator integrations are created in the default (last) Tier.
All Policies created by $[prodname] orchestrator integrations are created in the `default` Tier (order `1000000`), except Kubernetes ClusterNetworkPolicies, which are created in the `kube-admin` (order `1000`) and `kube-baseline` (order `10000000`) Tiers. If you install $[prodname] with the operator and the `projectcalico.org/v3` API is available (through the $[prodname] API server or v3 CRDs), the operator also creates a `calico-system` Tier (order `100`) for the policies it installs to allow $[prodname] component traffic.
Loading