Matthew Booth

@namgon-kim I fixed the linter issue in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/2211. Do you want to try rebasing this on top of current release-0.10 if you still need this?

/approve /lgtm

@lentzi90 Meta point: I recall you doing something similar before, but I can't find it to re-use it. I'm thinking of writing 2-4 of these in fairly quick succession, so...

I'm going to move this around to conform to the pattern set by https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1565

> Do we want to include a paragraph or two about if/how this could be used for [MachinePool support](https://cluster-api.sigs.k8s.io/tasks/experimental-features/machine-pools) in CAPO? From my understanding we would "just" need to add...

/remove-lifecycle stale

This is a valid issue, but simply because mutability for Subnet isn't implemented yet. We haven't implemented much mutability at all yet, tbh, only really enough to get a good...

https://github.com/kubernetes-sigs/controller-runtime/issues/1996 and some slack discussion: https://kubernetes.slack.com/archives/C02MRBMN00Z/p1738761791434629 tl;dr There is no current solution to this, but my assumption that a lookup from the informer cache can't fail (at least after initialisation)...

When you say 'returns an object', how did you generate this output? As you point out these fields have `omitempty`, so they should not be emitted when marshalling the object...

After a helpful conversation with a colleague I realised I've had a fundamental misunderstanding here: kubectl is rendering the object's stored values in full, as it does not have our...