-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.11
-
None
-
Moderate
-
None
-
5
-
Sprint 227, Sprint 228, Sprint 229, Sprint 230, Sprint 231, Sprint 232, Sprint 233, Sprint 234, Sprint 235, Sprint 236, Sprint 237, Sprint 238, Sprint 239, Sprint 240, Sprint 241, Sprint 242, Sprint 243, Sprint 244
-
18
-
Rejected
-
False
-
Description of problem:
As per the upstream update: https://github.com/kubernetes-sigs/external-dns/pull/2772. ExternalDNS is currently unable of handling multiple parallel instances (no leader election implemented). This may result into split brain situation during the rolling upgrades.
Version-Release number of selected component (if applicable):
1.1.0
How reproducible:
Manually
Steps to Reproduce:
1. Deploy any shipped version of ExternalDNS Operator 2. Create ExternalDNS CR 3. Check external-dns-operator namespace for the operand POD, see its update strategy set to RollingUpdate 4. Change the CR in anyway without breaking it (e.g. disable/enable hostname annotation) 5. See multiple operand PODs being active at the same time in external-dns-operator namespace
Actual results:
Multiple active operand PODs at the same time in external-dns-operator
Expected results:
Recreate strategy for the operand PODs, single deployment during the upgrades
Additional info:
- links to
-
RHEA-2023:123003
ExternalDNS Operator 1.2 operator/operand containers
