apidiff: ignore adding entirely new API groups

Adding the new Lifecycle API group caused apidiff to complain because
this situation had not been encountered when setting up the initial set of
allow rules and wasn't handled.

We don't need a CHANGELOG.md entry for this because it is a normal Go API
change, so the entry gets removed.

Before:

    Incompatible changes:
    - ./informers.SharedInformerFactory.Lifecycle: added

After:

    Acceptable incompatible changes:
    - ./informers.SharedInformerFactory.Lifecycle: added
    - ./kubernetes.Interface.LifecycleV1alpha1: added

Kubernetes-commit: 680f1dbde228b741b3b42774b448c48d0dfb20b3
This commit is contained in:
Patrick Ohly
2026-07-25 08:38:44 +02:00
committed by Kubernetes Publisher
parent 74d4b1ef91
commit 694f4ebe1b

View File

@@ -4,13 +4,6 @@ Go API changes are typically not included in the Kubernetes release notes, so
noteworthy Go API changes *may* be documented here. This is currently not
*required*, so consult the git history to see all changes.
### Introduce Lifecycle API group for v1alpha1 EvictionRequest and Eviction APIs
See [PR #137050](https://github.com/kubernetes/kubernetes/pull/137050)
```
- ./informers.SharedInformerFactory.Lifecycle: added
```
### Type-safe informers
All code using the result of the generated client-go Informer() methods (a