Skip to content

Commit 759dd6c

Browse files
committed
design-proposal(ip-address-claims): auto-claim into a non-default implementation is deferred
An auto-claimed Service has no loadBalancerClass and MetalLB reads no annotation in its place, so the default implementation serves it. State that as the field's semantics rather than a rule of this design, and defer auto-claim into a class of another implementation to a mutating admission webhook that sets the field at creation. Signed-off-by: Timofei Larkin <[email protected]> Assisted-by: LLM
1 parent 0129b2d commit 759dd6c

1 file changed

Lines changed: 9 additions & 5 deletions

File tree

‎design-proposals/ip-address-claims/README.md‎

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -497,11 +497,15 @@ placeholders carry the pool annotation, so this rule excludes them without the o
497497
annotation and without knowledge of the driver's namespace. The auto-claim class is
498498
independent of the default class.
499499

500-
An auto-claimed Service has no `loadBalancerClass`, and the core does not set one: the
501-
field is immutable and the Service already exists. The Service is therefore served by the
502-
implementation that handles unclassed Services, the cluster default (§1.5), and an
503-
auto-claim class must have an empty `loadBalancerClass`. The core ignores the auto-claim
504-
annotation on a class with a non-empty value and reports it with an event.
500+
An auto-claimed Service has no `loadBalancerClass`, so the cluster's default
501+
implementation serves it (§1.5). An auto-claim class is therefore a class of the default
502+
implementation, with an empty `loadBalancerClass`. This is the semantics of the field,
503+
not a rule of this design: the field is immutable once the Service is
504+
`type: LoadBalancer`, and MetalLB reads no annotation in its place, so no component can
505+
route an unclassed Service to another implementation after creation. The core reports an
506+
event on a class marked for auto-claim whose `loadBalancerClass` is non-empty, since no
507+
Service it mints for can be served. Auto-claim into such a class needs the field set at
508+
creation, which a mutating admission webhook could do from the class; that is deferred.
505509

506510
Two rules follow:
507511

0 commit comments

Comments
 (0)