It occurs to me that the kube-ovn charm should be doing more to inform the user about the mismatched config. This is a condition that the charm can easily check for, and it should enter a Blocked status with a clear message.
I was a little quick to mark this as invalid for kube-ovn. Sorry about that. :)
It occurs to me that the kube-ovn charm should be doing more to inform the user about the mismatched config. This is a condition that the charm can easily check for, and it should enter a Blocked status with a clear message.
I was a little quick to mark this as invalid for kube-ovn. Sorry about that. :)