quiet-architect-91246
08/03/2021, 7:20 PM"Container runtime not ready: cni not initialized".
This can be solved by running export kubever=$(kubectl version | base64 | tr -d '\n')
and kubectl apply -f "<https://cloud.weave.works/k8s/net?k8s-version=$kubever>"
. This obviously requires manual input which doesnt work for a automatic cicd pipeline, so Id love to do it in the declaration of the cluster with pulumi. I could hand in a recreation of the used .yaml file as ClusterRole
and ClusterRoleBinding
, but that would lead to very large, hardly readable codeblock and would require manual changes when the kubernetes version changes. Which leads me to my question: Is there a better way to handle the network initialization?billowy-army-68599
08/03/2021, 7:22 PMquiet-architect-91246
08/03/2021, 7:42 PM