Juan-Luis de Sousa-Valadas Castaño

Results 30 comments of Juan-Luis de Sousa-Valadas Castaño

K0s does not enable static pods by default, you can either enable it explicitly using the flag `--pod-manifest-path` [\[1\]]( https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/) [\[2\]](https://docs.k0sproject.io/head/worker-node-config/#kubelet-configuration) You can also consider using the [manifest deployer](https://docs.k0sproject.io/v1.28.5+k0s.0/manifests/) which...

> Kubernetes cronjob cannot access database service in other worker node when network policy is used. It works fine if I run sleep 3 command at first or all pods...

Are you 100% certain that the issue can be reproduced in 1.24.2 and not in 1.24.6, both using the OS version and hardware specs(to the extent of possible in VMs)?...

Well the fact that there isn't a regression is good. The policies are applied just not fast enough which means that Calico, after certain scale, will have the same issue....

After checking this further, `grpc.NewClient` ignores `grpc.WithBlock()`, so even if we pass a `grpc.WithContextDialer` it won't really have the effect we want. I think the most sensible way of dealing...

I made two changes: 1- Applied both suggestions. 2- Removed `gprc.WithBlock()` from the `grpc.NewClient` call. I apparently added it accidentally in the previous commit. This option is ignored in [grpc.NewClient](https://pkg.go.dev/google.golang.org/grpc#NewClient)...

Hi @leleobhz, > But a question that @juanluisvaladas awnser got me: If kube-proxy implements LoadBalancer, why this is not mentioned in https://docs.k0sproject.io/v1.28.5+k0s.0/examples/nginx-ingress/?h=loadbalance#install-nginx-using-loadbalancer as example? Neither kube-proxy or kube-router implement `LoadBalancer`...

Just for the reference, there is no need to provide a new kubeconfig, you can just grant additional permissions to the service account: https://github.com/k0sproject/k0s/issues/6340#issuecomment-3244951634

I rechecked this on fedora40, which is where I saw the issue in the first place and definitely couldn't reproduce. I must have done something wrong.