Mateusz Gozdek
Mateusz Gozdek
/remove-lifecycle stale
/remove-lifecycle stale
>Does this require kubernetes-sigs/cluster-api#4172 to merge first? For functioning correctly, yes, as it's using `ignition` API field.
CABPK PR kubernetes-sigs/cluster-api#4172 has been merged and will be part of v1.1 release, so we're getting closer getting this as well :tada:
I wonder, CAPI v1.1 RC release should be happening soon. I wonder if we can update CAPA main manifests to use it, so this PR could be merged.
I was thinking about updating https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/d352e7c6ea47974d8ec7c858cb76dea7e9d3ecc3/test/e2e/config/azure-dev.yaml#L60-L61 to CAPBK v1.1 rc1 release as an intermediate step before CAPBK v1.1 gets released, so we could merge this PR then.
>how do we test this template to make sure it doesn't regress? Hmm, so we're open to add e2e tests for Flatcar if you already have e2e tests for other...
>Hmm, so we're open to add e2e tests for Flatcar if you already have e2e tests for other flavors. But we need to sort out the issue with images first...
e2e tests passes, but I guess Flatcar cluster is not created then? Maybe some wiring is missing? I was using `kcp-scale-in` e2e test flavor as a reference.