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

feat: remove beta warning from image verify, exceptions and cleanup policy docs #1366

Merged
Merged
Show file tree
Hide file tree
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: 0 additions & 4 deletions content/en/docs/writing-policies/cleanup.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ description: >
weight: 70
---

{{% alert title="Warning" color="warning" %}}
Cleanup policies are a **beta** feature.
{{% /alert %}}

Kyverno has the ability to cleanup (i.e., delete) existing resources in a cluster in two different ways. The first way is via a declarative policy definition in either a `CleanupPolicy` or `ClusterCleanupPolicy`. See the section on [cleanup policies](#cleanup-policy) below for more details. The second way is via a reserved time-to-live (TTL) label added to a resource. See the [cleanup label](#cleanup-label) section for further details.

## Cleanup Policy
Expand Down
4 changes: 0 additions & 4 deletions content/en/docs/writing-policies/exceptions.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ description: >
weight: 80
---

{{% alert title="Warning" color="warning" %}}
Policy exceptions are a **beta** feature. Normal semantic versioning and compatibility rules will not apply.
{{% /alert %}}

Although Kyverno policies contain multiple methods to provide fine-grained control as to which resources they act upon in the form of [`match`/`exclude` blocks](match-exclude.md#match-statements), [preconditions](preconditions.md) at multiple hierarchies, [anchors](validate.md#anchors), and more, all these mechanisms have in common that the resources which they are intended to exclude must occur in the same rule definition. This may be limiting in situations where policies may not be directly editable, or doing so imposes an operational burden.

For example, in organizations where multiple teams must interact with the same cluster, a team responsible for policy authoring and administration may not be the same team responsible for submission of resources. In these cases, it can be advantageous to decouple the policy definition from certain exclusions. Additionally, there are often times where an organization or team must allow certain exceptions which would violate otherwise valid rules but on a one-time basis if the risks are known and acceptable.
Expand Down
4 changes: 0 additions & 4 deletions content/en/docs/writing-policies/verify-images/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ description: >
weight: 60
---

{{% alert title="Warning" color="warning" %}}
Image verification is a **beta** feature and there may be changes to the API.
{{% /alert %}}

The logical structure of an verifyImages rule is shown below:

<img src="/images/verify-image-rule.png" alt="Image Verification Rule" width="60%"/>
Expand Down
Loading