Guido Maria Serra+Fenaroli
Guido Maria Serra+Fenaroli
it all leads here, to the `kicker` but this setting seems to get ignored... ```yaml kubeadmConfigPatches: - | apiVersion: kubeadm.k8s.io/v1beta1 kind: ClusterConfiguration metadata: name: config apiServer: extraArgs: advertise-address: "0.0.0.0" ```
for reference, these refer to https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/#synopsis
nevermind... I tried to change the network layer to cilium, it is still happening
nothing, unstable even a plain installation without any config patching... plain `nvkind cluster create` loading our full stack, we have tons of pods restarting... it doesn't happen with a vanilla...
@elezar > Do you mean without injecting GPUs? i mean when starting just kind not through nvkind we had to switch in emergency to minikube: that worked out of the...
@romizhang I'm having a similar issue just when not using the public available fqdn... but the internal endpoint If i port forward the svc and mount it from my laptop...