apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:44:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: 1ca5b82c-eb4f-4995-a3f3-196227bbf7bd
    resourceVersion: "24168"
    uid: 9b298784-6a8f-4305-a08c-cb8630ee606c
  spec:
    sourcePod: network-check-source-7cbc45fddc-hwh7h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:51:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.084425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:38Z"
    - latency: 1.310559ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:38Z"
    - latency: 971.354µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:38Z"
    - latency: 1.094995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 902.372µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 973.798µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 786.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 877.323µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:38Z"
    - latency: 879.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:38Z"
    - latency: 1.042425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:44:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: 1ca5b82c-eb4f-4995-a3f3-196227bbf7bd
    resourceVersion: "22713"
    uid: 3e32d4c6-e8bf-4085-89aa-59c3c3f06310
  spec:
    sourcePod: network-check-source-7cbc45fddc-hwh7h
    targetEndpoint: a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:50:38Z"
      message: 'load-balancer-api-external: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.715298ms
      message: 'load-balancer-api-external: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 8.471449ms
      message: 'load-balancer-api-external: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 4.286209ms
      message: 'load-balancer-api-external: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 7.12269ms
      message: 'load-balancer-api-external: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 4.64138ms
      message: 'load-balancer-api-external: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 10.229142ms
      message: 'load-balancer-api-external: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 4.929194ms
      message: 'load-balancer-api-external: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 7.858455ms
      message: 'load-balancer-api-external: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 6.924065ms
      message: 'load-balancer-api-external: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:38Z"
    - latency: 8.520907ms
      message: 'load-balancer-api-external: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:58:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:44:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: 1ca5b82c-eb4f-4995-a3f3-196227bbf7bd
    resourceVersion: "22712"
    uid: 30242478-0ca4-45a5-a9d1-2a8fcaffad00
  spec:
    sourcePod: network-check-source-7cbc45fddc-hwh7h
    targetEndpoint: a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:50:38Z"
      message: 'load-balancer-api-internal: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.618942ms
      message: 'load-balancer-api-internal: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 8.527309ms
      message: 'load-balancer-api-internal: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 4.217348ms
      message: 'load-balancer-api-internal: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 7.172111ms
      message: 'load-balancer-api-internal: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 4.790477ms
      message: 'load-balancer-api-internal: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 10.166446ms
      message: 'load-balancer-api-internal: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 4.916834ms
      message: 'load-balancer-api-internal: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 7.903983ms
      message: 'load-balancer-api-internal: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 5.461013ms
      message: 'load-balancer-api-internal: tcp connection to a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:38Z"
    - latency: 8.468217ms
      message: 'load-balancer-api-internal: resolved host name a29217729f2404485b4f37c1bea4e2c5-bdd863b58a3e2e3c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:58:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:44:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-ip-10-0-130-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: 1ca5b82c-eb4f-4995-a3f3-196227bbf7bd
    resourceVersion: "24166"
    uid: a0885e06-3090-4397-9d9b-6bb947836385
  spec:
    sourcePod: network-check-source-7cbc45fddc-hwh7h
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:51:38Z"
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.197487ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:38Z"
    - latency: 2.312928ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:38Z"
    - latency: 2.196111ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:38Z"
    - latency: 2.161953ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 2.373727ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 2.20284ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 2.310346ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 2.117097ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:38Z"
    - latency: 2.311608ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:38Z"
    - latency: 2.401512ms
      message: 'network-check-target-ip-10-0-130-199: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:44:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-ip-10-0-141-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: 1ca5b82c-eb4f-4995-a3f3-196227bbf7bd
    resourceVersion: "24167"
    uid: c63a1987-d2f6-491f-8aa1-e35ac0e53f18
  spec:
    sourcePod: network-check-source-7cbc45fddc-hwh7h
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:51:38Z"
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.522083ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:38Z"
    - latency: 2.178694ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:38Z"
    - latency: 2.199246ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:38Z"
    - latency: 2.623658ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 2.169576ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 2.477299ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 2.303266ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 2.100948ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:38Z"
    - latency: 2.259365ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:38Z"
    - latency: 2.271374ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:44:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-ip-10-0-143-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: 1ca5b82c-eb4f-4995-a3f3-196227bbf7bd
    resourceVersion: "24165"
    uid: e3c415ba-6d7a-4d6f-b59e-0191c2972f23
  spec:
    sourcePod: network-check-source-7cbc45fddc-hwh7h
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:51:38Z"
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.676µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:38Z"
    - latency: 1.214268ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:38Z"
    - latency: 1.291352ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:38Z"
    - latency: 884.003µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 1.369396ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 1.028912ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 1.169675ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 1.18742ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:38Z"
    - latency: 1.209673ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:57:38Z"
    - latency: 1.062402ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:56:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:44:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: 1ca5b82c-eb4f-4995-a3f3-196227bbf7bd
    resourceVersion: "22711"
    uid: 5ed60cff-676d-4aba-a9ff-a863feeeff5c
  spec:
    sourcePod: network-check-source-7cbc45fddc-hwh7h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:50:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.269254ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 1.597086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:38Z"
    - latency: 898.997µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 1.748312ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:01:38Z"
    - latency: 786.014µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 1.943193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:00:38Z"
    - latency: 868.512µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 1.698549ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:59:38Z"
    - latency: 712.301µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:38Z"
    - latency: 2.030428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:58:38Z"
kind: List
metadata:
  resourceVersion: ""