Hello everyone,

I'm also a new contributer to XCP-ng!
For now I'll be working with @ronan-a on the SMAPIv3 plugins.
After that probably on open vSwitch.

Benjamin

The issue has been fixed on this branch, it'll be merged into master soon.

Perfect, see you on monday on the support ticket then!

Meanwhile, have a nice week end

Hello,

The DNS names of the master (and nodes also with a pattern) should be configurable for the user indeed. We'll add it in a next version of the recipe.

Thanks for the feedback!

Hi!

The fix is available on master.
You should be able to generate certificate now.

Yes it's 5396b90695fbe2c7a5f56d72a94a208517b2d517 but its not its only modification so it can't just be reverted.
This is a really quick fix I can push a branch today and it can be used waiting for the merge.

Hi!

In your Pool view there's a network tab where you can rename your networks by clicking on their name and enter a new one.

Regards.

Thanks

I'll try to investigate myself as well when i can, do not hesitate to come back here if you find anything.

And the pod network is made with kube-router: https://github.com/cloudnativelabs/kube-router/blob/master/docs/kubeadm.md

Ok thanks, then I don't understant why there's a pb unfortunately...

The recipe follow this doc to create the cluster: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/

@suaro how does your manual install differs from the doc used by the recipe? Perhaps we can dig there.

Did you make sure /proc/sys/net/bridge/bridge-nf-call-iptables is set to 1?

Our implementation uses kube-router wich requirest this setting.

Did the manual change solve the issue?

Ok, I'll try on my end to see if I encounter a similar error. Let me know how your next try goes.

Regards

Hello,

Can the master communicate with the other nodes? What IP ranges did you use for kubernetes CIDR & for your VM IPs?

Thanks

@d1rtym0nk3y If DHCP is configured on your network then yes.

Perhaps what you can try is having VLAN15 CIDR goes from 10.0.15.0 to 10.0.15.n and the CIDR for kubernetes going from 10.0.15.n+1 to 10.0.15.254 and you're router addressing the whole 10.0.15.X range?

What do you think?