Open brunda-bs opened 1 month ago
triage: our upgrade policy allows to upgrade 2 minor versions, so you should upgrade from
2.5.2
to2.7.6
and then from2.7.6
to2.8.2
. Also are you sure you upgraded global first?
@brunda-bs any news?
Hi @lukidzi / @slonka
Yes, We did upgrade the global first.
triage: did you also upgraded as suggested from 2.5.x to 2.7.x first and then from 2.7.x to 2.8.x?
What happened?
We are trying to upgrade Kuma from 2.5.2 to 2.8.2. We see an issue with external service connectivity post-upgrade. We have 500+ external services in our current setup.
Kuma control plane error logs:
2024-08-06T04:34:30.568Z ERROR vips-outbound-view there are two external services with the same 'networking.address' or two headless services, to disable automatic DNS generation in external services set 'networking.disableHostDNSEntry=true' in at least one of these externalService {"error": "autogenerated DNS entry cpmsignal-training.xyz-digital.net:443 from external-service:cpmsignal-training-xyz-digital-net-443-4vvvf74fbw6w4vz6 conflicts with existing entry external-service:cpmsignal-training-xyz-digital-net-443"}
Looks like the above error is due to the metadata name changes for the external service in zone tenants post-upgrade. Although the error disappears after 10-15 minutes, the application container is failing to establish connectivity to the external service as it is failing with a connection refused error or failed to resolve the external DNS error.
The external services that were created in 2.5 were having the metadata.name -
cpmsignal-training-xyz-digital-net-443.
After the upgrade global cp still using the same but somehow the Zone cp is recreating a local copy of the external service configuration with a different metadata.name.cpmsignal-training-xyz-digital-net-443-4vvvf74fbw6w4vz6
Global CP external service:
Zone CP external service: