Mateusz Gozdek
Mateusz Gozdek
@mauriciovasquezbernal thanks, let me give it a try :)
Seems to work correctly, cool, thank you for fixing it @blanquicet! :tada:
not stale please
not stale please
Hm, as far as I remember and understand, this is not a new behavior in v0.9.0, it has always been like this. This is because in K8s nodes are expected...
Interesting. Thank you for sharing your use case. I understand your rationale, but considering that the behavior did not change between the releases as far as I know, I would...
It seems to me with 1.3.0 enabling LTO builds just fine, so perhaps this can be closed? In case you try it @dvzrv, perhaps you can also add `-X github.com/containernetworking/plugins/pkg/utils/buildversion.BuildVersion=${pkgver}'`...
The same thing is happening when deploying Azure CCM on Flatcar: https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/3387#issuecomment-1495684214 it seems.
Thanks for helping out @jepio. I was going to suggest a custom dependency to update_engine service too, since as far as I know this is the official mechanism for extending...
I think that sounds reasonable. We should be able to extend our periodic system with that if we agree on some reasonable notation.