apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-135-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-135.ec2.internal
      uid: 42933e55-f8fa-47bc-b90e-ad3760140555
    resourceVersion: "53684"
    uid: c21a32a3-938e-4584-b9c0-8a42089294f5
  spec:
    sourcePod: network-check-source-989f8b8dc-sjwnf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:13:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.051953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 978.069µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 977.393µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 853.812µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:38:40Z"
    - latency: 1.228035ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:37:40Z"
    - latency: 984.914µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:36:40Z"
    - latency: 858.564µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:35:40Z"
    - latency: 932.822µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:34:40Z"
    - latency: 930.437µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:33:40Z"
    - latency: 933.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:32:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-135-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-135.ec2.internal
      uid: 42933e55-f8fa-47bc-b90e-ad3760140555
    resourceVersion: "54580"
    uid: 239130ce-9a1e-436e-88c5-b9671f9f8ab1
  spec:
    sourcePod: network-check-source-989f8b8dc-sjwnf
    targetEndpoint: a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:12:40Z"
      message: 'load-balancer-api-external: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.38831ms
      message: 'load-balancer-api-external: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:42:40Z"
    - latency: 8.627115ms
      message: 'load-balancer-api-external: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:42:40Z"
    - latency: 6.114191ms
      message: 'load-balancer-api-external: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 8.248572ms
      message: 'load-balancer-api-external: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 3.68982ms
      message: 'load-balancer-api-external: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 8.267063ms
      message: 'load-balancer-api-external: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 4.20365ms
      message: 'load-balancer-api-external: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 7.963861ms
      message: 'load-balancer-api-external: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 5.182164ms
      message: 'load-balancer-api-external: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:38:40Z"
    - latency: 7.446091ms
      message: 'load-balancer-api-external: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:38:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-135-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-135.ec2.internal
      uid: 42933e55-f8fa-47bc-b90e-ad3760140555
    resourceVersion: "54579"
    uid: 03274642-129a-45f8-a311-78fc846375a4
  spec:
    sourcePod: network-check-source-989f8b8dc-sjwnf
    targetEndpoint: a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:12:40Z"
      message: 'load-balancer-api-internal: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.923631ms
      message: 'load-balancer-api-internal: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:42:40Z"
    - latency: 8.550977ms
      message: 'load-balancer-api-internal: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:42:40Z"
    - latency: 3.789305ms
      message: 'load-balancer-api-internal: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 8.292678ms
      message: 'load-balancer-api-internal: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 4.807114ms
      message: 'load-balancer-api-internal: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 8.32515ms
      message: 'load-balancer-api-internal: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 4.320949ms
      message: 'load-balancer-api-internal: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 8.05911ms
      message: 'load-balancer-api-internal: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 5.160956ms
      message: 'load-balancer-api-internal: tcp connection to a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:38:40Z"
    - latency: 7.533308ms
      message: 'load-balancer-api-internal: resolved host name a1482d0b4af584d8da1514eb806854ed-d8a7c608a5de1043.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:38:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-135-to-network-check-target-ip-10-0-131-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-135.ec2.internal
      uid: 42933e55-f8fa-47bc-b90e-ad3760140555
    resourceVersion: "53681"
    uid: 684879a6-60f8-417c-b940-17f7633d3acb
  spec:
    sourcePod: network-check-source-989f8b8dc-sjwnf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:13:40Z"
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 750.074µs
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 1.375707ms
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 985.064µs
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 901.602µs
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:38:40Z"
    - latency: 995.682µs
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:37:40Z"
    - latency: 1.053177ms
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:36:40Z"
    - latency: 910.329µs
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:35:40Z"
    - latency: 1.424526ms
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:34:40Z"
    - latency: 959.333µs
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:33:40Z"
    - latency: 890.218µs
      message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:32:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-135-to-network-check-target-ip-10-0-135-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-135.ec2.internal
      uid: 42933e55-f8fa-47bc-b90e-ad3760140555
    resourceVersion: "53682"
    uid: 49b4ea74-93bc-4d48-8bee-fd58651236d4
  spec:
    sourcePod: network-check-source-989f8b8dc-sjwnf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:13:40Z"
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.13086ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 2.174921ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 2.420117ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 2.332557ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:38:40Z"
    - latency: 2.141366ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:37:40Z"
    - latency: 2.574048ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:36:40Z"
    - latency: 2.339784ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:35:40Z"
    - latency: 2.214879ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:34:40Z"
    - latency: 2.219506ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:33:40Z"
    - latency: 2.276887ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:32:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-135-to-network-check-target-ip-10-0-137-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-135.ec2.internal
      uid: 42933e55-f8fa-47bc-b90e-ad3760140555
    resourceVersion: "53683"
    uid: c3502619-5e37-4f77-ada4-bf1f7c11ba3d
  spec:
    sourcePod: network-check-source-989f8b8dc-sjwnf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:13:40Z"
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.556324ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 2.414479ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 2.576285ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 2.08087ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:38:40Z"
    - latency: 2.604884ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:37:40Z"
    - latency: 2.115744ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:36:40Z"
    - latency: 2.234767ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:35:40Z"
    - latency: 2.313596ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:34:40Z"
    - latency: 2.491623ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:33:40Z"
    - latency: 2.69622ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:32:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-135-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-135.ec2.internal
      uid: 42933e55-f8fa-47bc-b90e-ad3760140555
    resourceVersion: "54578"
    uid: 16d3539f-8738-4a77-9877-01bba725a37d
  spec:
    sourcePod: network-check-source-989f8b8dc-sjwnf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:12:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.364µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:42:40Z"
    - latency: 1.805581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:42:40Z"
    - latency: 1.185932ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 1.694801ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:41:40Z"
    - latency: 1.200923ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 1.85873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:40:40Z"
    - latency: 1.089849ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 1.731235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:39:40Z"
    - latency: 902.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:38:40Z"
    - latency: 2.128498ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:38:40Z"
kind: List
metadata:
  resourceVersion: ""