apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:29:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-212-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-212.us-east-2.compute.internal
      uid: 1d144e43-4cd3-483a-ba07-7cb51062424e
    resourceVersion: "107617"
    uid: 26b0004d-8cad-4a90-b91c-13cecca4fccf
  spec:
    sourcePod: network-check-source-6f78d59f99-sfhm7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:36:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.188079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 1.128894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 930.939µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 912.734µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 966.149µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:07:21Z"
    - latency: 1.251603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:06:21Z"
    - latency: 964.559µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:05:21Z"
    - latency: 4.605311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:04:21Z"
    - latency: 1.365851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:03:21Z"
    - latency: 1.42423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:02:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:29:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-212-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-212.us-east-2.compute.internal
      uid: 1d144e43-4cd3-483a-ba07-7cb51062424e
    resourceVersion: "107619"
    uid: 223c1bd3-efde-4ceb-b9e4-3da1724becad
  spec:
    sourcePod: network-check-source-6f78d59f99-sfhm7
    targetEndpoint: a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:35:21Z"
      message: 'load-balancer-api-external: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.068325ms
      message: 'load-balancer-api-external: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 8.148882ms
      message: 'load-balancer-api-external: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 5.05521ms
      message: 'load-balancer-api-external: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 8.813482ms
      message: 'load-balancer-api-external: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 6.431622ms
      message: 'load-balancer-api-external: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 7.448736ms
      message: 'load-balancer-api-external: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 5.524679ms
      message: 'load-balancer-api-external: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 10.302345ms
      message: 'load-balancer-api-external: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 5.295438ms
      message: 'load-balancer-api-external: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:07:21Z"
    - latency: 9.376709ms
      message: 'load-balancer-api-external: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:07:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:29:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-212-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-212.us-east-2.compute.internal
      uid: 1d144e43-4cd3-483a-ba07-7cb51062424e
    resourceVersion: "107618"
    uid: 18b58284-221c-4b3b-a7da-3d4fdbdd0b63
  spec:
    sourcePod: network-check-source-6f78d59f99-sfhm7
    targetEndpoint: a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:35:21Z"
      message: 'load-balancer-api-internal: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.081877ms
      message: 'load-balancer-api-internal: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 8.06064ms
      message: 'load-balancer-api-internal: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 4.983205ms
      message: 'load-balancer-api-internal: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 8.778264ms
      message: 'load-balancer-api-internal: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 5.829301ms
      message: 'load-balancer-api-internal: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 7.580298ms
      message: 'load-balancer-api-internal: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 5.472533ms
      message: 'load-balancer-api-internal: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 10.26618ms
      message: 'load-balancer-api-internal: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 5.243821ms
      message: 'load-balancer-api-internal: tcp connection to a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:07:21Z"
    - latency: 9.346111ms
      message: 'load-balancer-api-internal: resolved host name a6b5a7adc45b04eaaba9850be40fd57e-1002c69fc8cc21af.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:07:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:29:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-212-to-network-check-target-ip-10-0-128-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-212.us-east-2.compute.internal
      uid: 1d144e43-4cd3-483a-ba07-7cb51062424e
    resourceVersion: "107614"
    uid: 46903aa4-4f03-4bff-bfb6-cd651e707d2a
  spec:
    sourcePod: network-check-source-6f78d59f99-sfhm7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:36:21Z"
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.104743ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 2.096328ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 2.055822ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 2.294124ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 1.864587ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:07:21Z"
    - latency: 2.763456ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:06:21Z"
    - latency: 2.154121ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:05:21Z"
    - latency: 6.891232ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:04:21Z"
    - latency: 2.361209ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:03:21Z"
    - latency: 2.177484ms
      message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:02:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:29:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-212-to-network-check-target-ip-10-0-133-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-212.us-east-2.compute.internal
      uid: 1d144e43-4cd3-483a-ba07-7cb51062424e
    resourceVersion: "107615"
    uid: 6594060a-73ce-4bd7-a9f1-391ea358caec
  spec:
    sourcePod: network-check-source-6f78d59f99-sfhm7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:36:21Z"
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.298825ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 2.368862ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 2.34881ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 2.26511ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 2.35283ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:07:21Z"
    - latency: 2.283633ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:06:21Z"
    - latency: 2.178094ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:05:21Z"
    - latency: 4.656203ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:04:21Z"
    - latency: 2.439914ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:03:21Z"
    - latency: 2.272236ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:02:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:29:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-212-to-network-check-target-ip-10-0-143-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-212.us-east-2.compute.internal
      uid: 1d144e43-4cd3-483a-ba07-7cb51062424e
    resourceVersion: "107612"
    uid: 039653af-a218-4bd5-baec-41ffcfac4709
  spec:
    sourcePod: network-check-source-6f78d59f99-sfhm7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:36:21Z"
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.352023ms
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 918.67µs
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 1.440911ms
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 1.020669ms
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 1.08146ms
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:07:21Z"
    - latency: 932.893µs
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:06:21Z"
    - latency: 1.881638ms
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:05:21Z"
    - latency: 4.383024ms
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:04:21Z"
    - latency: 957.815µs
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:03:21Z"
    - latency: 1.007826ms
      message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:02:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:29:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-212-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-212.us-east-2.compute.internal
      uid: 1d144e43-4cd3-483a-ba07-7cb51062424e
    resourceVersion: "107613"
    uid: 46b91abe-bd9f-4aea-9b5a-6c2268378c72
  spec:
    sourcePod: network-check-source-6f78d59f99-sfhm7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:35:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.839615ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 1.849639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:11:21Z"
    - latency: 1.043377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 2.289809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:10:21Z"
    - latency: 967.485µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 1.69704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:09:21Z"
    - latency: 1.272014ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 1.662388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:08:21Z"
    - latency: 1.154529ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:07:21Z"
    - latency: 1.902474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:07:21Z"
kind: List
metadata:
  resourceVersion: ""