apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:58:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c0ce5948-34ac-4be1-adae-27654acc9b5e
    resourceVersion: "28856"
    uid: abf5ab6b-4f06-49f5-8864-914d1f760556
  spec:
    sourcePod: network-check-source-56499946bc-jjs2h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:05:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:12:01Z"
    - latency: 886.584µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:11:01Z"
    - latency: 1.081219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 1.129504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 1.143187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 1.05366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 1.207912ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:06:01Z"
    - latency: 1.128499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:05:01Z"
    - latency: 1.713422ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:04:01Z"
    - latency: 1.027909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:03:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:58:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c0ce5948-34ac-4be1-adae-27654acc9b5e
    resourceVersion: "27275"
    uid: 5c73b404-0a37-41eb-9ec7-10ee0bbecb17
  spec:
    sourcePod: network-check-source-56499946bc-jjs2h
    targetEndpoint: a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:04:01Z"
      message: 'load-balancer-api-external: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.847892ms
      message: 'load-balancer-api-external: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 7.369414ms
      message: 'load-balancer-api-external: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 6.544133ms
      message: 'load-balancer-api-external: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 10.087991ms
      message: 'load-balancer-api-external: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 4.949165ms
      message: 'load-balancer-api-external: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 7.267624ms
      message: 'load-balancer-api-external: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 4.767864ms
      message: 'load-balancer-api-external: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 7.201665ms
      message: 'load-balancer-api-external: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 3.459037ms
      message: 'load-balancer-api-external: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:06:01Z"
    - latency: 7.462736ms
      message: 'load-balancer-api-external: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:06:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:58:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c0ce5948-34ac-4be1-adae-27654acc9b5e
    resourceVersion: "27274"
    uid: 64598338-a4fa-49dc-8321-4ba29da85d02
  spec:
    sourcePod: network-check-source-56499946bc-jjs2h
    targetEndpoint: a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:04:01Z"
      message: 'load-balancer-api-internal: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.531868ms
      message: 'load-balancer-api-internal: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 7.397944ms
      message: 'load-balancer-api-internal: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 6.567407ms
      message: 'load-balancer-api-internal: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 10.185125ms
      message: 'load-balancer-api-internal: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 4.227626ms
      message: 'load-balancer-api-internal: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 7.223223ms
      message: 'load-balancer-api-internal: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 4.751853ms
      message: 'load-balancer-api-internal: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 7.227722ms
      message: 'load-balancer-api-internal: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 4.740824ms
      message: 'load-balancer-api-internal: tcp connection to a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:06:01Z"
    - latency: 7.496279ms
      message: 'load-balancer-api-internal: resolved host name a09172a7e34f04b6583231ca2b2fd7f3-1a325b55baed55e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:06:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:58:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-ip-10-0-131-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c0ce5948-34ac-4be1-adae-27654acc9b5e
    resourceVersion: "28855"
    uid: f3f2dc0d-de17-485d-965a-1d130ad9a3f8
  spec:
    sourcePod: network-check-source-56499946bc-jjs2h
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:05:01Z"
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.025484ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:12:01Z"
    - latency: 2.307118ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:11:01Z"
    - latency: 2.324736ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 2.375321ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 2.219677ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 2.233147ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 2.12085ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:06:01Z"
    - latency: 2.348993ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:05:01Z"
    - latency: 2.26199ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:04:01Z"
    - latency: 2.269974ms
      message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:03:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:58:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-ip-10-0-131-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c0ce5948-34ac-4be1-adae-27654acc9b5e
    resourceVersion: "28854"
    uid: b978c92f-8174-48b9-9817-b5deabe84e99
  spec:
    sourcePod: network-check-source-56499946bc-jjs2h
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:05:01Z"
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.915178ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:12:01Z"
    - latency: 1.897166ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:11:01Z"
    - latency: 1.919418ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 2.072955ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 1.650592ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 1.987175ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 1.8657ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:06:01Z"
    - latency: 1.927158ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:05:01Z"
    - latency: 1.948576ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:04:01Z"
    - latency: 2.148958ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:03:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:58:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-ip-10-0-139-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c0ce5948-34ac-4be1-adae-27654acc9b5e
    resourceVersion: "28853"
    uid: 9e309ea5-5fd3-4b59-8981-7ffb00f3c20a
  spec:
    sourcePod: network-check-source-56499946bc-jjs2h
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:05:01Z"
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095092ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:12:01Z"
    - latency: 1.281691ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:11:01Z"
    - latency: 1.455349ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 844.234µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 1.028572ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 1.0382ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 854.938µs
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:06:01Z"
    - latency: 1.520793ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:05:01Z"
    - latency: 1.702844ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:04:01Z"
    - latency: 1.019725ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:03:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:58:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-59-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-59.ec2.internal
      uid: c0ce5948-34ac-4be1-adae-27654acc9b5e
    resourceVersion: "27272"
    uid: cd174213-f335-4aaa-8ccb-63beaa3538be
  spec:
    sourcePod: network-check-source-56499946bc-jjs2h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T16:04:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.565µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 1.624698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:10:01Z"
    - latency: 855.534µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 1.755514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:09:01Z"
    - latency: 997.431µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 1.733264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:08:01Z"
    - latency: 1.13709ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 1.680142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:07:01Z"
    - latency: 1.034959ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T16:06:01Z"
    - latency: 1.824641ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T16:06:01Z"
kind: List
metadata:
  resourceVersion: ""