apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T02:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.us-east-2.compute.internal
      uid: fdb416d1-7350-423e-8a39-624e26903f9e
    resourceVersion: "117883"
    uid: d4c29327-4f03-4aa7-9ab5-eac8e5696359
  spec:
    sourcePod: network-check-source-6f78d59f99-zp7jw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:05:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 934.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 1.572055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 1.082139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 1.360153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:36:11Z"
    - latency: 1.878253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:35:11Z"
    - latency: 813.821µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:34:11Z"
    - latency: 973.141µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:33:11Z"
    - latency: 1.312072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:32:11Z"
    - latency: 1.094151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T02:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.us-east-2.compute.internal
      uid: fdb416d1-7350-423e-8a39-624e26903f9e
    resourceVersion: "117885"
    uid: 2e44cf96-aa3e-4e0c-9b3a-68256eb05b60
  spec:
    sourcePod: network-check-source-6f78d59f99-zp7jw
    targetEndpoint: aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:04:11Z"
      message: 'load-balancer-api-external: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.73974ms
      message: 'load-balancer-api-external: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 7.846183ms
      message: 'load-balancer-api-external: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 4.770941ms
      message: 'load-balancer-api-external: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 8.581755ms
      message: 'load-balancer-api-external: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 4.681746ms
      message: 'load-balancer-api-external: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 7.264744ms
      message: 'load-balancer-api-external: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 4.724786ms
      message: 'load-balancer-api-external: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 8.371278ms
      message: 'load-balancer-api-external: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 6.246606ms
      message: 'load-balancer-api-external: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:36:11Z"
    - latency: 8.181803ms
      message: 'load-balancer-api-external: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:36:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T02:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.us-east-2.compute.internal
      uid: fdb416d1-7350-423e-8a39-624e26903f9e
    resourceVersion: "117886"
    uid: 8bd78816-9888-4c07-a033-0d57fdb06b29
  spec:
    sourcePod: network-check-source-6f78d59f99-zp7jw
    targetEndpoint: aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:04:11Z"
      message: 'load-balancer-api-internal: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.758272ms
      message: 'load-balancer-api-internal: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 7.665905ms
      message: 'load-balancer-api-internal: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 3.869235ms
      message: 'load-balancer-api-internal: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 8.482361ms
      message: 'load-balancer-api-internal: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 4.64937ms
      message: 'load-balancer-api-internal: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 7.301286ms
      message: 'load-balancer-api-internal: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 4.278976ms
      message: 'load-balancer-api-internal: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 8.26712ms
      message: 'load-balancer-api-internal: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 6.296179ms
      message: 'load-balancer-api-internal: tcp connection to aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:36:11Z"
    - latency: 8.086745ms
      message: 'load-balancer-api-internal: resolved host name aa733b65ef3094b0fb799b886b31fc3b-d36336563c40d93b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:36:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T02:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-ip-10-0-129-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.us-east-2.compute.internal
      uid: fdb416d1-7350-423e-8a39-624e26903f9e
    resourceVersion: "117881"
    uid: 78e17e54-c733-4c6a-be34-4602a720e708
  spec:
    sourcePod: network-check-source-6f78d59f99-zp7jw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:05:11Z"
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.035085ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 2.345276ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 2.385074ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 2.452318ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 2.324659ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:36:11Z"
    - latency: 2.321431ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:35:11Z"
    - latency: 1.897404ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:34:11Z"
    - latency: 2.191511ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:33:11Z"
    - latency: 2.395283ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:32:11Z"
    - latency: 2.168056ms
      message: 'network-check-target-ip-10-0-129-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T02:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-ip-10-0-130-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.us-east-2.compute.internal
      uid: fdb416d1-7350-423e-8a39-624e26903f9e
    resourceVersion: "117879"
    uid: f8ccac4c-610c-4db5-b583-6be673366f36
  spec:
    sourcePod: network-check-source-6f78d59f99-zp7jw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:05:11Z"
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.173826ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 863.158µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 1.580489ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 1.011447ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 1.492982ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:36:11Z"
    - latency: 1.420147ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:35:11Z"
    - latency: 787.595µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:34:11Z"
    - latency: 1.041254ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:33:11Z"
    - latency: 1.064427ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:32:11Z"
    - latency: 1.305613ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T02:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-ip-10-0-139-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.us-east-2.compute.internal
      uid: fdb416d1-7350-423e-8a39-624e26903f9e
    resourceVersion: "117880"
    uid: b157d9d1-cf52-4c14-984d-8e787b4ad6c1
  spec:
    sourcePod: network-check-source-6f78d59f99-zp7jw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:05:11Z"
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.423687ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 2.204765ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 2.448043ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 2.147463ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 2.289777ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:36:11Z"
    - latency: 2.093241ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:35:11Z"
    - latency: 1.820171ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:34:11Z"
    - latency: 2.23001ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:33:11Z"
    - latency: 2.417788ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:32:11Z"
    - latency: 2.235338ms
      message: 'network-check-target-ip-10-0-139-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T02:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.us-east-2.compute.internal
      uid: fdb416d1-7350-423e-8a39-624e26903f9e
    resourceVersion: "117882"
    uid: c482f260-cb9c-4c56-b276-0496111ef2d5
  spec:
    sourcePod: network-check-source-6f78d59f99-zp7jw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:04:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026673ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 2.148027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:40:11Z"
    - latency: 1.037997ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 1.814224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:39:11Z"
    - latency: 1.056757ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 2.007442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:38:11Z"
    - latency: 852.85µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 1.748437ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:37:11Z"
    - latency: 1.04487ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T03:36:11Z"
    - latency: 2.07291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T03:36:11Z"
kind: List
metadata:
  resourceVersion: ""