Joel Speed

I expect we need to follow the aliases to find out the underlying type and apply the checks that we are applying to the underlying type once we hit a...

The workaround described in https://github.com/kubernetes/kubernetes/issues/132370#issuecomment-3053492022 is not actually compatible with a `resource.Quantity` completely. Bear in mind that a Quantity of `0` is valid, and with the workaround, this would only...

Take a look at the API schema that is generated, with the workaround you have: ``` size: type: string ``` Where an int-or-string would be ``` size: anyOf: - type:...

The MachineSet webhook defaults an empty selector to include the `MachineSetNameLabel` with the `m.Name` value, but there is currently no validation that the value of that label matches `m.Name` I...

> Wondering if we should move a step further and do not expose selectors in the API 🤔 Would that mean relying solely on owner references to find the Machines...

Hey @MisterMX, can you explain more about the use case here? I'm curious in which scenario would you want to have a field in the type but not generated within...

Can you provide a concrete example to where this is used? When you say the definitions are added by crossplane, does that mean that the fields are populated by crossplane...

I'd suggest we start by introducing and using both old and new versions of the finalizers for a release, before removing them in a subsequent release. It wouldn't be a...

> I guess relying on this only makes sense if they try to implement some sort of ordering (maybe?) around finalizers. Which feels a bit like an anti-pattern? This has...

@vr4manta Is this a bug backport? Previously we could add more vcenters, but that wasn't supported? What, apart from this API is required here to complete this?