Marcus Noble
Marcus Noble
It's not something I'm currently able to work on but I wanted to make sure the feature was at least tracked here as Flatcar has a ticket tracking progress across...
Here's the PR in CAPA adding support - https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/2271
/remove-lifecycle stale
/remove-lifecycle stale /lifecycle frozen
@t-lo FYI I've opened an issue on CAPG to request Flatcar support - https://github.com/kubernetes-sigs/cluster-api-provider-gcp/issues/540
I can't currently as have other work with higher priorities but possibly in the future once this becomes more of a priority for us. I mainly wanted to ensure it...
I'm not sure if adding it to `MachineDeployments` makes sense. `MachinePools` leverage the providers built-in scaling functionality (e.g. AWS ASGs) which have a lot of existing scalers available without needing...
I think that issue might be unrelated to this. This issue aims to solve the problem where the autoscaler runs somewhere other than the management cluster - e.g. cluster-autoscaler running...
> and just to repeat for clarity, the cluster-autoscaler is doing option 1. it relies on the cluster-api controllers to make the new machine and add it to the cluster....
@Skarlso @richardcase would I be correct that this relates to both managed and unmanaged VPCs? If so I know there's some [current logic](https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/13617fa198118cf8ffbcf252584da15a23445dd9/pkg/cloud/services/network/subnets.go#L109-L116) that requires a CAPA-managed VPC to have...