Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bpickard22 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
bde2828 to
0989e92
Compare
|
@bpickard22 : please rebase this on top of #1838 (meaning include Ric's commits and then yours as well - otherwise we won't be able to see the CI on the actual thing before you hand it to Ric and he will have to fix stuff) : I'd like to see a green CI on Interconnect, as far as alerts are concerned. |
0989e92 to
911d7fe
Compare
- Determine OVN interconnect zone mode by inspecting an (optional) configMap; apply the desired zone mode. - upgrade from non-IC to IC OVN-K by going through an intermediate step with 1-zone - Switch from IC single zone to IC multizone (as in upgrades) and back (not fully supported yet, for internal use only) Avoid clashes between single-zone ovnkube-master (using ports 9102, 9641, 9642, 29102) and multizone ovnkube-node (initially using ports 9103, 9105, 9102, 29102, 29103) during upgrade from 4.13 and avoid using ports reserved for the storage components, as described in https://github.com/openshift/enhancements/blob/master/dev-guide/host-port-registry.md This caused the storage operator to never be available after installation of or upgrade to 4.14. In multizone ovnkube-node let's now have: - 9103, 9105, 29103 (which don't collide with single-zone ovnkube-master) - 9112, 9112 9113, 29113 so as to not collide with single-zone ovnkube-master Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
In the very last step of the 2-phase upgrade to OVN interconnect, we remove the IC configmap. At this point, SetFromPods from pod_status.go won't be called any more, because all changes to the daemonsets have been processed. Patch the ovnk master daemonset with a dummy annotation to trigger status recalculation. TODO: find a better way to run SetFromPods instead of updating ovnk master annotations Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Beware: this goes with https://github.com/openshift/ovn-kubernetes/pull/1727/commits Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
In ovn-ic there will be no raft as each node will have its own instance of the databases, so we can remove the raft related alerts Signed-off-by: Ben Pickard <bpickard@redhat.com>
Refactor alerts to run based off new metric names in ovn-ic Signed-off-by: Ben Pickard <bpickard@redhat.com>
911d7fe to
4289b01
Compare
|
@bpickard22: The following tests 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. |
|
PR needs rebase. 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. |
PR to allow for review only, this commit will be given to @ricky-rav as part of his work in CNO for ovn-ic
@ricky-rav i need some eyes on the labels for the service monitor to make sure I am using the right syntax
Also need someone from the monitoring team to take a look at the alert expressions to make sure I am going about that correctly