Ambiguous change of ovn networks

[gecube]

Hi!

If somebody installs cozy-stack with some kind of configmap:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cozystack
  namespace: cozy-system
data:
  bundle-name: "paas-full"
  ipv4-pod-cidr: "100.64.0.0/16"
  ipv4-pod-gateway: "10.64.0.1"
  ipv4-svc-cidr: "10.65.0.0/16"
  ipv4-join-cidr: "100.66.0.0/16"

it gives the broken installation. The pods are mainly running, but ovn is failing. The possible solution could be to change the configmap values to the proper ones like:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cozystack
  namespace: cozy-system
data:
  bundle-name: "paas-full"
  ipv4-pod-cidr: "100.64.0.0/16"
  ipv4-pod-gateway: "100.64.0.1"
  ipv4-svc-cidr: "100.65.0.0/16"
  ipv4-join-cidr: "100.66.0.0/16"

but unfortunately they are not applied on-the-fly. One needs to remove ovn installation with helm means and reapply it again to make cozystack installation proceed.

I think we should investigate this issue and probably make some warning and / or document workaround.

[kvaps]

Could you please report issue to upstream project?

[dosubot[bot]]

Hi, @gecube. I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that setting certain OVN network CIDR values in a ConfigMap breaks the cozy-stack installation.
• OVN fails despite pods running, and changes to CIDR require uninstalling and reinstalling OVN via Helm.
• The issue stems from the inability to apply CIDR changes dynamically.
• You suggested investigating this and adding warnings or documentation for a workaround.
• A maintainer recommended reporting the issue to the upstream project for further assistance.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of cozy-stack by commenting here.
• If I don’t hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!