fix: Ignore serviceSpec.ClusterIPs when comparing services to prevent endless routing reconciliation loop#504
Conversation
… endless routing r<!-- Please provide instructions here how reviewer can test your changes if applicable -->econciliation loop. The field was introduced in Kubernetes 1.20.
f442226 to
36f25bc
Compare
|
/test v7-devworkspaces-operator-e2e |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amisevsk, JPinkney, metlos, sleshchenko The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test v7-devworkspaces-operator-e2e, v7-devworkspace-happy-path |
1 similar comment
|
/test v7-devworkspaces-operator-e2e, v7-devworkspace-happy-path |
|
@metlos: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
from e2e test, devworkspace-controller:
|
|
Hmm... so this boils down to the difference in |
|
New changes are detected. LGTM label has been removed. |
|
/test |
|
@metlos: The
Use
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/test v7-devworkspaces-operator-e2e |
|
Tests passed. I'll take care of it and sync with PR on devfile/api side |
|
/test v7-devworkspace-happy-path |
|
I have troubles with updated DWO to devfile/api#565. Tested the current state and everything seems to work:
|
|
/test v7-devworkspace-happy-path |
What does this PR do?
The field
clusterIPswas introduced in Kubernetes 1.20. We're not ignoring it when reconciling the services and because it is automatically set by Kubernetes, it causes a permanent difference between the intended spec and the actual spec preventing the controller from finishing the reconciliation of a devworkspace routing.What issues does this PR fix or reference?
N/A
Is it tested? How?
Only manually.
PR Checklist
/test v7-devworkspaces-operator-e2e, v7-devworkspace-happy-pathto trigger)v7-devworkspaces-operator-e2e: DevWorkspace e2e testv7-devworkspace-happy-path: DevWorkspace e2e test