You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have many clusters created before this change, which don't have that block at all in the terraform state, and when we apply with the new version we get:
# module.oke.module.oke.oci_containerengine_cluster.k8s_cluster must be replaced-/+resource"oci_containerengine_cluster""k8s_cluster" {
[...]
+cluster_pod_network_options { # forces replacement+cni_type="FLANNEL_OVERLAY"# forces replacement
}
which is really bad as it leads to whole cluster recreation even though we didn't want any changes to the network type.
Is this something I should bring to the provider? Or maybe it's something solved by updating kube to 1.24+?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
This might be an issue of the terraform provider or even a OCI-wide issue, but I hope the folks here can shed some light.
Version 4.2.6 introduced native pod networking and with them this block:
terraform-oci-oke/modules/oke/cluster.tf
Lines 19 to 21 in ffe6524
in the cluster resource.
We have many clusters created before this change, which don't have that block at all in the terraform state, and when we apply with the new version we get:
which is really bad as it leads to whole cluster recreation even though we didn't want any changes to the network type.
Is this something I should bring to the provider? Or maybe it's something solved by updating kube to 1.24+?
All reactions