* feature: Add LabelSelector as a field of resource spec to allow fetching by labels
Signed-off-by: aerosouund <aerosound161@gmail.com>
* chore: Generate CRDs
Signed-off-by: aerosouund <aerosound161@gmail.com>
* feat: Add the capability to fetch with label selector
- Add the label selector as a parameter to GetResources of the engine api client and the dclient.
- Use the label selector with list options in the dclient.
- convert a metav1.LabelSelector to a labels.Selector before fetching to be able to convert it to a string to be used with ListOptions.
Signed-off-by: aerosouund <aerosound161@gmail.com>
* feat: Pass label selector to the GetResources method
Signed-off-by: aerosouund <aerosound161@gmail.com>
* feat: Return the resource selector when resolving spec
Signed-off-by: aerosouund <aerosound161@gmail.com>
* fix: Instantiate the fake client schema using the passed gvrToListKind map and by inferring schema from passed resources
All tests that use List will fail because the fake client doesn't infer the schema from the passed resources.
gvrToListKind can't be fully deprecated as some parts of kyverno use the fake client without passing resources to it (resource generation). And so both approaches have to be supported.
References:
- https://github.com/kubernetes/client-go/issues/983
-
|
||
---|---|---|
.devcontainer | ||
.github | ||
.vscode | ||
api | ||
charts | ||
cmd | ||
config | ||
data | ||
docs | ||
ext | ||
hack | ||
img | ||
litmuschaos | ||
pkg | ||
scripts | ||
test | ||
.chainsaw.yaml | ||
.codeclimate.yml | ||
.directory | ||
.gitignore | ||
.golangci.yml | ||
.goreleaser.yml | ||
.ko.yaml | ||
.krew.yaml | ||
.nancy-ignore | ||
ADOPTERS.md | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
CONTRIBUTORS.md | ||
DEVELOPMENT.md | ||
go.mod | ||
go.sum | ||
GOVERNANCE.md | ||
LICENSE | ||
MAINTAINERS.md | ||
Makefile | ||
OWNERS.md | ||
README.md | ||
ROADMAP.md | ||
SECURITY-INSIGHTS.yml | ||
SECURITY.md | ||
sonar-project.properties |
Kyverno 
Cloud Native Policy Management 🎉
Kyverno is a policy engine designed for cloud native platform engineering teams. It enables security, automation, compliance, and governance using policy-as-code. Kyverno can validate, mutate, generate, and cleanup configurations using Kubernetes admission controls, background scans, and source code respository scans. Kyverno policies can also be used to verify OCI images, for software supply chain security. Kyverno policies can be managed as Kubernetes resources and do not require learning a new language. Kyverno is designed to work nicely with tools you already use like kubectl, kustomize, and Git.
📙 Documentation
Kyverno installation and reference documents are available at [kyverno.io] (https://kyverno.io).
🙋♂️ Getting Help
We are here to help!
👉 For feature requests and bugs, file an issue.
👉 For discussions or questions, join the Kyverno Slack channel.
👉 For community meeting access, see mailing list.
👉 To get follow updates ⭐️ star this repository.
➕ Contributing
Thanks for your interest in contributing to Kyverno! Here are some steps to help get you started:
✔ Read and agree to the Contribution Guidelines.
✔ Browse through the GitHub discussions.
✔ Read Kyverno design and development details on the GitHub Wiki.
✔ Check out the good first issues list. Add a comment with /assign
to request assignment of the issue.
✔ Check out the Kyverno Community page for other ways to get involved.
Software Bill of Materials
All Kyverno images include a Software Bill of Materials (SBOM) in CycloneDX JSON format. SBOMs for Kyverno images are stored in a separate repository at ghcr.io/kyverno/sbom
. More information on this is available at Fetching the SBOM for Kyverno.
Contributors
Kyverno is built and maintained by our growing community of contributors!
Made with contributors-img.
License
Copyright 2024, the Kyverno project. All rights reserved. Kyverno is licensed under the Apache License 2.0.
Kyverno is a Cloud Native Computing Foundation (CNCF) Incubating project and was contributed by Nirmata.