Enhance cluster CIDR creation logic on TrueNAS SCALE
Description
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Waqar March 12, 2021 at 5:35 PM
Ah, so yeah that change was added after 21.02. Fingers crossed for the BETA version 😉
jonas libbrecht March 12, 2021 at 5:30 PM
Hi @Waqar, I am not working on the most recent MASTER branch. I am currently on TrueNAS-SCALE-21.02-ALPHA.1
Will update/reinstall when the BETA version will be released (sometime real soon 🙂 ?)
Waqar March 12, 2021 at 5:21 PM
@jonas libbrecht can you please confirm on which TN version you experienced this ? We have added some logic in recent MASTER which should do a best effort to judge CIDRs in use and pick one which is not being used.
jonas libbrecht March 12, 2021 at 5:19 PM
Hold on, @Kjeld Schouten-lebbing the core product here is still Truenas and not kubernetes. So insulting somebody here that this is a layer 8 bug is a no-go.
I experienced this problem also in my setup found this ticket, and I read this as: like docker/kubernetes has claimed this, everybody should know this.
There is some much to learn in IT and one should not pretend that one knows everything.
Kjeld Schouten-lebbing December 31, 2020 at 12:55 PM
While this would be nice:
Picking the docker/kubernetes default range for your real network, is basically also a layer 8 bug...
Cluster CIDR defaults to 172.16.0.0/16, which can conflict with other networks configured elesewhere. This should be more intelligent and check if network is not used elsewhere (even with narrower mask) OR there should be dialog asking what network should be created. For now, after initial install i'm always need to disable k8s bridge and change addressation of the cluster.