Skip to content

docs: add Secure-by-Default Kubernetes technical outcome#2053

Open
Suhani95 wants to merge 1 commit into
kyverno:mainfrom
Suhani95:Secure-by-Default-Kubernetes
Open

docs: add Secure-by-Default Kubernetes technical outcome#2053
Suhani95 wants to merge 1 commit into
kyverno:mainfrom
Suhani95:Secure-by-Default-Kubernetes

Conversation

@Suhani95
Copy link
Copy Markdown
Contributor

Related issue

Related to kyverno/kyverno#15990

Proposed Changes

Adds a new Technical Outcomes documentation page for Secure-by-Default Kubernetes.

The page connects Kyverno capabilities such as validation, mutation, generate policies, image verification, and policy reports to secure Kubernetes operations and governance.

Included content

  • problem space and common Kubernetes security risks
  • desired operational outcomes
  • Kyverno capability overview
  • real-world security use cases
  • example Kyverno policies
  • outcome mapping
  • implementation guidance
  • related resources and documentation

Checklist

  • I have read the contributing guidelines.
  • I have inspected the website preview for accuracy.
  • I have signed off my issue.

Signed-off-by: Suhani <suhani4630@gmail.com>
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label May 29, 2026
@kkrypt0nn
Copy link
Copy Markdown

Considering ClusterPolicy is getting deprecated, people should move to the respective ValidatingPolicy, MutatingPolicy and GeneratingPolicy.

Hence I do believe new documentation shouldn't use ClusterPolicy as it gives people reading it already a deprecated start into the project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants