Files

Jiahui Feng 049614f884 ValidatingAdmissionPolicy controller for Type Checking (#117377 )

* [API REVIEW] ValidatingAdmissionPolicyStatucController config.

worker count.

* ValidatingAdmissionPolicyStatus controller.

* remove CEL typechecking from API server.

* fix initializer tests.

* remove type checking integration tests

from API server integration tests.

* validatingadmissionpolicy-status options.

* grant access to VAP controller.

* add defaulting unit test.

* generated: ./hack/update-codegen.sh

* add OWNERS for VAP status controller.

* type checking test case.

2023-07-13 13:41:50 -07:00

aggregator_violation_exceptions.list

Update generated files

2023-02-27 14:16:02 -05:00

apiextensions_violation_exceptions.list

include apiextensions types in apiextensions generated openapi

2023-05-01 13:18:44 -07:00

codegen_violation_exceptions.list

Update generated files

2023-02-27 14:16:02 -05:00

README.md

Remove generated file rules in make

2022-10-04 08:50:30 -07:00

sample_apiserver_violation_exceptions.list

Update generated files

2023-02-27 14:16:02 -05:00

violation_exceptions.list

ValidatingAdmissionPolicy controller for Type Checking (#117377 )

2023-07-13 13:41:50 -07:00

README.md

Existing API Rule Violations

This folder contains the checked-in report file of known API rule violations. The file violation_exceptions.list is used by Make rule during OpenAPI spec generation to make sure that no new API rule violation is introduced into our code base.

API Rule Violation Format

The report file violation_exceptions.list is in format of:

API rule violation: <RULE>,<PACKAGE>,<TYPE>,<FIELD>

e.g.

API rule violation: names_match,k8s.io/api/core/v1,Event,ReportingController

And the violation list is sorted alphabetically in each of the <RULE>, <PACKAGE>, <TYPE>, <FIELD> levels.

How to resolve API Rule Check Failure

Make rule returns an error when the newly generated violation report differs from this checked-in violation report.

Our goal is that exceptions should never be added to this list, only fixed and removed. For new APIs, this is a hard requirement. For APIs that are e.g. being moved between versions or groups without other changes, it is OK for your API reviewer to make an exception.

If you're removing violations from the exception list, or if you have good reasons to add new violations to this list, please update the file using:

UPDATE_API_KNOWN_VIOLATIONS=true ./hack/update-codegen.sh

It is up to API reviewers to review the list and make sure new APIs follow our API conventions.

NOTE: please don't hide changes to this file in a "generated changes" commit, treat it as source code instead.

API Rules Being Enforced

For more information about the API rules being checked, please refer to https://github.com/kubernetes/kube-openapi/tree/master/pkg/generators/rules