feat: object count quota enforcement and webhook for core/extended resources #67
+3,785
−2,230
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Pull Request
📖 Description
This PR implements object count quota enforcement for native and extended Kubernetes resources in the PAC Quota Controller.
What problem does this solve?
How did you solve it?
Key changes:
ObjectCountWebhook
andServiceWebhook
for admission control.Chart.yaml
,README.md
,README.md.gotmpl
,values.yaml
, CRDs, RBAC, webhook config) updated.📚 Documentation
Updated Helm chart documentation (
README.md
,README.md.gotmpl
,values.yaml
)Expanded CRD documentation for object count quotas
Added API comments and examples for all supported resources
📖 Updated documentation
📄 Added examples
Testing & Validation
pre-commit run --all-files
(runs formatting, linting, generation, and unit tests)make test-e2e
(ensure e2e tests pass - not included in pre-commit)Versioning & Release
version
incharts/pac-quota-controller/Chart.yaml
if making a chart changeappVersion
incharts/pac-quota-controller/Chart.yaml
if releasing a new application versionvX.Y.Z
for app releases orchart-vX.Y.Z
for chart-only releases (if applicable)