apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:40:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-223.ec2.internal
      uid: 71f5a414-dbb2-4bc4-8160-56a20dff736a
    resourceVersion: "54270"
    uid: 80f80901-cb15-4a88-b7c6-6cbba790689c
  spec:
    sourcePod: network-check-source-869dcfcdcd-8gw65
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T21:47:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 1.183101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 1.110686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 1.339617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:12:50Z"
    - latency: 933.958µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:11:50Z"
    - latency: 905.158µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:10:50Z"
    - latency: 943.323µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:09:50Z"
    - latency: 990.186µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:08:50Z"
    - latency: 997.919µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:07:50Z"
    - latency: 1.046324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:06:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:40:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-223.ec2.internal
      uid: 71f5a414-dbb2-4bc4-8160-56a20dff736a
    resourceVersion: "55177"
    uid: 12121cb0-9b8c-48a0-8c7b-76f9ae262b2a
  spec:
    sourcePod: network-check-source-869dcfcdcd-8gw65
    targetEndpoint: a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T21:46:50Z"
      message: 'load-balancer-api-external: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.793584ms
      message: 'load-balancer-api-external: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:16:50Z"
    - latency: 9.096963ms
      message: 'load-balancer-api-external: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:16:50Z"
    - latency: 5.214258ms
      message: 'load-balancer-api-external: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 7.864837ms
      message: 'load-balancer-api-external: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 7.328607ms
      message: 'load-balancer-api-external: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 9.337267ms
      message: 'load-balancer-api-external: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 4.190885ms
      message: 'load-balancer-api-external: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 7.203092ms
      message: 'load-balancer-api-external: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 4.939869ms
      message: 'load-balancer-api-external: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:12:50Z"
    - latency: 8.783061ms
      message: 'load-balancer-api-external: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:12:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:40:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-223.ec2.internal
      uid: 71f5a414-dbb2-4bc4-8160-56a20dff736a
    resourceVersion: "55176"
    uid: 0885bcf9-6b59-49ed-9762-67328c5f92c1
  spec:
    sourcePod: network-check-source-869dcfcdcd-8gw65
    targetEndpoint: a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T21:46:50Z"
      message: 'load-balancer-api-internal: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.908397ms
      message: 'load-balancer-api-internal: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:16:50Z"
    - latency: 9.075399ms
      message: 'load-balancer-api-internal: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:16:50Z"
    - latency: 5.153603ms
      message: 'load-balancer-api-internal: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 7.923062ms
      message: 'load-balancer-api-internal: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 6.069904ms
      message: 'load-balancer-api-internal: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 9.441796ms
      message: 'load-balancer-api-internal: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 4.060774ms
      message: 'load-balancer-api-internal: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 7.226827ms
      message: 'load-balancer-api-internal: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 3.540049ms
      message: 'load-balancer-api-internal: tcp connection to a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:12:50Z"
    - latency: 8.800471ms
      message: 'load-balancer-api-internal: resolved host name a8383ecd7773240129fc460c0a1b5dfc-9f99fd1f67abf244.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:12:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:40:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-223-to-network-check-target-ip-10-0-128-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-223.ec2.internal
      uid: 71f5a414-dbb2-4bc4-8160-56a20dff736a
    resourceVersion: "54267"
    uid: 4637dd5f-261b-420e-8376-896784269e5d
  spec:
    sourcePod: network-check-source-869dcfcdcd-8gw65
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T21:47:50Z"
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.647701ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 1.781208ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 1.587696ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 1.940049ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:12:50Z"
    - latency: 1.690674ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:11:50Z"
    - latency: 1.675587ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:10:50Z"
    - latency: 1.854773ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:09:50Z"
    - latency: 1.986894ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:08:50Z"
    - latency: 1.639101ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:07:50Z"
    - latency: 1.783496ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:06:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:40:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-223-to-network-check-target-ip-10-0-130-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-223.ec2.internal
      uid: 71f5a414-dbb2-4bc4-8160-56a20dff736a
    resourceVersion: "54268"
    uid: 00100600-7dfe-4b97-b95b-fa3bc1827923
  spec:
    sourcePod: network-check-source-869dcfcdcd-8gw65
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T21:47:50Z"
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.005µs
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 1.070318ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 1.008959ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 937.733µs
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:12:50Z"
    - latency: 959.439µs
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:11:50Z"
    - latency: 820.443µs
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:10:50Z"
    - latency: 1.046513ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:09:50Z"
    - latency: 912.43µs
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:08:50Z"
    - latency: 897.566µs
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:07:50Z"
    - latency: 1.356311ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:06:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:40:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-223-to-network-check-target-ip-10-0-131-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-223.ec2.internal
      uid: 71f5a414-dbb2-4bc4-8160-56a20dff736a
    resourceVersion: "54269"
    uid: cf162dc5-88c1-41fe-bf3e-873afc272f6a
  spec:
    sourcePod: network-check-source-869dcfcdcd-8gw65
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T21:47:50Z"
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.468127ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 2.320189ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 2.234124ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 2.552996ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:12:50Z"
    - latency: 2.013221ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:11:50Z"
    - latency: 1.789522ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:10:50Z"
    - latency: 2.238799ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:09:50Z"
    - latency: 2.070877ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:08:50Z"
    - latency: 2.289235ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:07:50Z"
    - latency: 2.294344ms
      message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:06:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T21:40:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-223.ec2.internal
      uid: 71f5a414-dbb2-4bc4-8160-56a20dff736a
    resourceVersion: "55175"
    uid: dea78305-df07-4660-ac4b-078ef67620ba
  spec:
    sourcePod: network-check-source-869dcfcdcd-8gw65
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T21:46:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.212978ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:16:50Z"
    - latency: 1.867631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:16:50Z"
    - latency: 1.04524ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 1.896666ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:15:50Z"
    - latency: 885.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 1.796344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:14:50Z"
    - latency: 862.158µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 1.739468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:13:50Z"
    - latency: 932.496µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:12:50Z"
    - latency: 1.928207ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:12:50Z"
kind: List
metadata:
  resourceVersion: ""