1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-05 07:26:55 +00:00

Optimize the tables and partial descriptions in the document (#6017)

Signed-off-by: Fish-pro <zechun.chen@daocloud.io>

Signed-off-by: Fish-pro <zechun.chen@daocloud.io>
This commit is contained in:
Fish-pro 2023-01-18 14:34:14 +08:00 committed by GitHub
parent 858c82e4bc
commit 4ab3c88e67
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 22 additions and 22 deletions

View file

@ -9,24 +9,24 @@ Note: There are several other organizations and users that are unable to publicl
The list of organizations that have publicly shared the usage of Kyverno:
| Organization | Success Story |
| :--- | :--- |
| [Amazon EKS Best Practice Guides](https://github.com/aws/aws-eks-best-practices/tree/master/policies/kyverno) | Policies for security and best practices |
| [Arrikto Inc.](https://www.arrikto.com) | Kubeflow policies |
| [Flux2](https://github.com/fluxcd/flux2-multi-tenancy#enforce-tenant-isolation) | Manage multi-tenancy and tenant isolation with GitOps |
| [Nirmata](https://nirmata.com) | Kubernetes Policy and Governance |
| [Ohio Supercomputer Center](https://www.osc.edu/) | Support Kubernetes multi-user workflows through [Open OnDemand](http://openondemand.org/) |
| [Coinbase](https://www.coinbase.com/) | Use Kyverno for mutation, to replace hand-written Webhooks, and generation to project common Kubernetes objects into many similar namespaces. |
| [Mandiant](https://www.mandiant.com/) | Use Kyverno for policy enforcement in all clusters, as well as part of our onboarding systems, populating new namespaces with requisite resources and secrets. |
| [Giant Swarm](https://www.giantswarm.io/) | Use Kyverno extensively to handle defaulting logic on resources (primarily cluster-api resources) and some scenarios to replace PSPs to enforce certain restrictions. |
| [Vodafone Group Plc](https://www.vodafone.com/) | Policy enforcement and automation on an internal k8s service offering. |
| [Deutsche Telekom](https://www.telekom.com/en) | Use Kyverno to enforce Policies on managed clusters to prevent right escalation of internal customers and to enforce security rules. |
| [VSHN AG - APPUiO Cloud](https://www.vshn.ch/) | OpenShift Multi-Tenancy Self-Service for [APPUiO Cloud](https://www.appuio.ch), managed with [Project Syn](https://syn.tools). Kyverno policies are available on [GitHub](https://github.com/appuio/component-appuio-cloud). |
| [Bloomberg](https://www.techatbloomberg.com/) | Use Kyverno for replacing custom validation and mutation webhooks in their internal Kubernetes based platforms |
| [Techcombank](https://www.techcombank.com.vn/trang-chu) | Use Kyverno to enforce security policies rules, Kubernetes best practices for their internal container based workload on Kubernetes|
| [Trendyol](https://www.trendyol.com) | In adoption planning to roll out to hundreds of production clusters using GitOps |
| [Rafay Systems](https://rafay.co/) | Platform supports centralized deployment of Kyverno across clusters|
| [Wayfair](https://wayfair.com) | Policy enforcement on managed clusters. Replacement of some in-house mutating webhooks. |
| Organization | Success Story |
|:--------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [Amazon EKS Best Practice Guides](https://github.com/aws/aws-eks-best-practices/tree/master/policies/kyverno) | Policies for security and best practices |
| [Arrikto Inc.](https://www.arrikto.com) | Kubeflow policies |
| [Flux2](https://github.com/fluxcd/flux2-multi-tenancy#enforce-tenant-isolation) | Manage multi-tenancy and tenant isolation with GitOps |
| [Nirmata](https://nirmata.com) | Kubernetes Policy and Governance |
| [Ohio Supercomputer Center](https://www.osc.edu/) | Support Kubernetes multi-user workflows through [Open OnDemand](http://openondemand.org/) |
| [Coinbase](https://www.coinbase.com/) | Use Kyverno for mutation, to replace hand-written Webhooks, and generation to project common Kubernetes objects into many similar namespaces. |
| [Mandiant](https://www.mandiant.com/) | Use Kyverno for policy enforcement in all clusters, as well as part of our onboarding systems, populating new namespaces with requisite resources and secrets. |
| [Giant Swarm](https://www.giantswarm.io/) | Use Kyverno extensively to handle defaulting logic on resources (primarily cluster-api resources) and some scenarios to replace PSPs to enforce certain restrictions. |
| [Vodafone Group Plc](https://www.vodafone.com/) | Policy enforcement and automation on an internal k8s service offering. |
| [Deutsche Telekom](https://www.telekom.com/en) | Use Kyverno to enforce Policies on managed clusters to prevent right escalation of internal customers and to enforce security rules. |
| [VSHN AG - APPUiO Cloud](https://www.vshn.ch/) | OpenShift Multi-Tenancy Self-Service for [APPUiO Cloud](https://www.appuio.ch), managed with [Project Syn](https://syn.tools). Kyverno policies are available on [GitHub](https://github.com/appuio/component-appuio-cloud). |
| [Bloomberg](https://www.techatbloomberg.com/) | Use Kyverno for replacing custom validation and mutation webhooks in their internal Kubernetes based platforms |
| [Techcombank](https://www.techcombank.com.vn/trang-chu) | Use Kyverno to enforce security policies rules, Kubernetes best practices for their internal container based workload on Kubernetes |
| [Trendyol](https://www.trendyol.com) | In adoption planning to roll out to hundreds of production clusters using GitOps |
| [Rafay Systems](https://rafay.co/) | Platform supports centralized deployment of Kyverno across clusters |
| [Wayfair](https://wayfair.com) | Policy enforcement on managed clusters. Replacement of some in-house mutating webhooks. |
<!-- append the line below to the table
| [name](URL) | brief description of how you are using Kyverno |
-->

View file

@ -42,7 +42,7 @@ New contributors may easily view all [open issues labeled as good first issues](
Once you wish to get started contributing to the code base, please refer to our [running in development mode](https://github.com/kyverno/kyverno/wiki/Running-in-development-mode) for local setup guide.
In the process of submitting your PRs, please read and abide by the template provided to ensure the maintainers are able to understand your changes and quickly come up to speed. There are some important pieces that are required outside of the code itself. Some of these are up to you, others are up to the maintainers.
In the process of submitting your PRs, please read and abide by the template provided to ensure the maintainers are able to understand your changes and quickly come up to speed. There are some important pieces that are required outside the code itself. Some of these are up to you, others are up to the maintainers.
1. Provide Proof Manifests allowing the maintainers and other contributors to verify your changes without requiring they understand the nuances of all your code.
2. For new or changed functionality, this typically requires documentation and so raise a corresponding issue (or, better yet, raise a separate PR) on the [documentation repository](https://github.com/kyverno/website).
@ -113,7 +113,7 @@ git cherry-pick <commit-hash> -s
git push --set-upstream origin release-1.7
```
Once the commit has been cherry picked, the author will need to open a PR merging to the release branch, release-1.7 for example.
Once the commit has been cherry-picked, the author will need to open a PR merging to the release branch, release-1.7 for example.
#### Developer Certificate of Origin (DCO) Sign off

View file

@ -384,7 +384,7 @@ You can run Kyverno locally or in your IDE of choice with a few steps:
1. Create a local cluster
- You can create a simple cluster with [KinD](https://kind.sigs.k8s.io/) with `make kind-create-cluster`
1. Deploy Kyverno manifests except the Kyverno `Deployment`
- Kyverno is going to run on your local machine so it should not run in cluster at the same time
- Kyverno is going to run on your local machine, so it should not run in cluster at the same time
- You can deploy the manifests by running `make debug-deploy`
1. To run Kyverno locally against the remote cluster you will need to provide `--kubeconfig` and `--serverIP` arguments:
- `--kubeconfig` must point to your kubeconfig file (usually `~/.kube/config`)

View file

@ -3,7 +3,7 @@
Maintainers are approvers who have shown good technical judgement in guiding feature design & development, have displayed overall knowledge of the project and features in the project, and are nurturing and receptive to everyone in the community.
| Maintainer | GitHub ID | Affiliation |
| ------------------------ | ------------------------------------------------------ | ------------------------- |
|--------------------------|--------------------------------------------------------|---------------------------|
| Jim Bugwadia | [@JimBugwadia](https://github.com/JimBugwadia) | Nirmata |
| Shuting Zhao | [@realshuting](https://github.com/realshuting) | Nirmata |
| Chip Zoller | [@chipzoller](https://github.com/chipzoller) | Nirmata |