Christian Schlotter
Christian Schlotter
MachineSetPreflightChecks + maxSurge zero results in MDs downscaled for a time longer than desirable
Note: it is possible to disable MachineSetPreflightChecks, but if you are using kubeadm it may expose you to other issues. Before implementing a solution please share a possible solution here...
Took a quick look at autoscalers code. For me it looks like they don't handle that the daemonset controller schedules a new pod. They ignore that fact but seem to...
To better understand your use-case: Are the Compute Cluster's A/B in the different zones the same ones? Rephrased: Is `Zone A / Compute Cluster A` the same as `Zone B...
I think this should work by declaring the Zone and Region as the datacenter, instead of wanting to declare multiple compute clusters as single zone: ```yaml apiVersion: infrastructure.cluster.x-k8s.io/v1beta1 kind: VSphereFailureDomain...
(note: verified in a test environment, but it only contained a single compute cluster)
Note: also verified with having a second cluster which is part of the same datacenter.
Ah its the same / single datacenter 🤔 I expected Zone A / Zone B / Zone C to be different datacenters. Can you explain some more about the use...
So to draw a small picture here which only highlights the MachineDeployment view for now, what you want to accomplish is something like this:  You have * A single...
/hold we need to validate this with tests "manually" before mreging /ok-to-test
xref: govmomi support for sha256 thumbprints: - https://github.com/vmware/govmomi/pull/3384 Should be part of the next govmomi release. --- Thanks @neolit123 for sumarizing. Regarding support of sha256 thumbprints: - We now have...