apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T22:06:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-41.us-west-2.compute.internal
      uid: 1b4f0a0d-7579-445c-8ec4-fdea05b5a230
    resourceVersion: "78369"
    uid: d0f999f9-2af2-4811-a983-1486927210d1
  spec:
    sourcePod: network-check-source-6f78d59f99-4t246
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T22:13:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.206996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:55:41Z"
    - latency: 992.592µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:54:41Z"
    - latency: 1.290791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:53:41Z"
    - latency: 1.188895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:52:41Z"
    - latency: 1.258978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:51:41Z"
    - latency: 1.178058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:50:41Z"
    - latency: 1.198253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:49:41Z"
    - latency: 1.550133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:48:41Z"
    - latency: 1.086136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:47:41Z"
    - latency: 1.37525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T22:06:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-41.us-west-2.compute.internal
      uid: 1b4f0a0d-7579-445c-8ec4-fdea05b5a230
    resourceVersion: "81506"
    uid: 9d1f5318-1562-4c38-8515-59f88566f45a
  spec:
    sourcePod: network-check-source-6f78d59f99-4t246
    targetEndpoint: ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T22:12:41Z"
      message: 'load-balancer-api-external: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.894197ms
      message: 'load-balancer-api-external: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T23:00:41Z"
    - latency: 6.471321ms
      message: 'load-balancer-api-external: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T23:00:41Z"
    - latency: 56.16116ms
      message: 'load-balancer-api-external: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:59:41Z"
    - latency: 7.200474ms
      message: 'load-balancer-api-external: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:59:41Z"
    - latency: 56.256369ms
      message: 'load-balancer-api-external: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:58:41Z"
    - latency: 6.687137ms
      message: 'load-balancer-api-external: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:58:41Z"
    - latency: 54.928666ms
      message: 'load-balancer-api-external: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:57:41Z"
    - latency: 8.126719ms
      message: 'load-balancer-api-external: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:57:41Z"
    - latency: 52.09082ms
      message: 'load-balancer-api-external: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:56:41Z"
    - latency: 6.851011ms
      message: 'load-balancer-api-external: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:56:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T22:06:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-41.us-west-2.compute.internal
      uid: 1b4f0a0d-7579-445c-8ec4-fdea05b5a230
    resourceVersion: "81507"
    uid: 7202e494-11b3-4059-96b6-4b8923255921
  spec:
    sourcePod: network-check-source-6f78d59f99-4t246
    targetEndpoint: ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T22:12:41Z"
      message: 'load-balancer-api-internal: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 61.950871ms
      message: 'load-balancer-api-internal: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T23:00:41Z"
    - latency: 6.441159ms
      message: 'load-balancer-api-internal: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T23:00:41Z"
    - latency: 51.972175ms
      message: 'load-balancer-api-internal: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:59:41Z"
    - latency: 7.222605ms
      message: 'load-balancer-api-internal: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:59:41Z"
    - latency: 53.744869ms
      message: 'load-balancer-api-internal: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:58:41Z"
    - latency: 6.660996ms
      message: 'load-balancer-api-internal: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:58:41Z"
    - latency: 54.939623ms
      message: 'load-balancer-api-internal: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:57:41Z"
    - latency: 7.894141ms
      message: 'load-balancer-api-internal: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:57:41Z"
    - latency: 62.388944ms
      message: 'load-balancer-api-internal: tcp connection to ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:56:41Z"
    - latency: 6.817328ms
      message: 'load-balancer-api-internal: resolved host name ac0a2f50c2ab94c12807d3b1c760afba-8cfc36a42c20be03.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:56:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T22:06:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-41-to-network-check-target-ip-10-0-130-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-41.us-west-2.compute.internal
      uid: 1b4f0a0d-7579-445c-8ec4-fdea05b5a230
    resourceVersion: "78363"
    uid: f5901fd3-f1ce-43fa-bc9b-f8ffcac374e8
  spec:
    sourcePod: network-check-source-6f78d59f99-4t246
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T22:13:41Z"
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.596µs
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:55:41Z"
    - latency: 1.435277ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:54:41Z"
    - latency: 1.211564ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:53:41Z"
    - latency: 1.182054ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:52:41Z"
    - latency: 970.378µs
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:51:41Z"
    - latency: 1.621418ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:50:41Z"
    - latency: 1.361498ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:49:41Z"
    - latency: 1.786578ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:48:41Z"
    - latency: 1.40459ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:47:41Z"
    - latency: 800.521µs
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T22:06:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-41-to-network-check-target-ip-10-0-140-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-41.us-west-2.compute.internal
      uid: 1b4f0a0d-7579-445c-8ec4-fdea05b5a230
    resourceVersion: "78472"
    uid: 14d0a7d8-6c56-4460-9209-455ce744527b
  spec:
    sourcePod: network-check-source-6f78d59f99-4t246
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T22:13:50Z"
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.786316ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:55:50Z"
    - latency: 2.629442ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:54:50Z"
    - latency: 2.606344ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:53:50Z"
    - latency: 2.534053ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:52:50Z"
    - latency: 978.325µs
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:51:50Z"
    - latency: 2.724475ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:50:50Z"
    - latency: 1.235818ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:49:50Z"
    - latency: 1.216572ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:48:50Z"
    - latency: 7.196696ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:47:50Z"
    - latency: 2.330244ms
      message: 'network-check-target-ip-10-0-140-221: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:46:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T22:06:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-41-to-network-check-target-ip-10-0-143-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-41.us-west-2.compute.internal
      uid: 1b4f0a0d-7579-445c-8ec4-fdea05b5a230
    resourceVersion: "78364"
    uid: b4d9f55d-1072-4b76-88c7-dad702c4a122
  spec:
    sourcePod: network-check-source-6f78d59f99-4t246
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T22:13:41Z"
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.463118ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:55:41Z"
    - latency: 2.432954ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:54:41Z"
    - latency: 2.759567ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:53:41Z"
    - latency: 3.133526ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:52:41Z"
    - latency: 3.128311ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:51:41Z"
    - latency: 2.984476ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:50:41Z"
    - latency: 2.437515ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:49:41Z"
    - latency: 2.793538ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:48:41Z"
    - latency: 2.291169ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:47:41Z"
    - latency: 2.309611ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T22:06:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-41.us-west-2.compute.internal
      uid: 1b4f0a0d-7579-445c-8ec4-fdea05b5a230
    resourceVersion: "81505"
    uid: 9f4e7455-e091-41bb-af83-dad9b51a7ddd
  spec:
    sourcePod: network-check-source-6f78d59f99-4t246
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T22:12:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.098µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T23:00:41Z"
    - latency: 1.838122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T23:00:41Z"
    - latency: 921.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:59:41Z"
    - latency: 2.444946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:59:41Z"
    - latency: 787.494µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:58:41Z"
    - latency: 1.674939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:58:41Z"
    - latency: 1.302971ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:57:41Z"
    - latency: 2.032051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:57:41Z"
    - latency: 823.69µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T22:56:41Z"
    - latency: 1.904331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T22:56:41Z"
kind: List
metadata:
  resourceVersion: ""