apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:09:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-10-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-10.ec2.internal
      uid: 79564ff7-2106-4e74-8e20-4771af93f396
    resourceVersion: "20547"
    uid: 66a2df07-9ae2-47b4-90d8-dd6b3747120f
  spec:
    sourcePod: network-check-source-6f8b768455-8rz9j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T07:16:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.070853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:30:12Z"
    - latency: 1.099035ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:29:12Z"
    - latency: 874.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:28:12Z"
    - latency: 791.4µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 1.754838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 1.491979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 1.083646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 909.623µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:23:12Z"
    - latency: 1.156283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:22:12Z"
    - latency: 1.059057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:09:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-10-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-10.ec2.internal
      uid: 79564ff7-2106-4e74-8e20-4771af93f396
    resourceVersion: "19386"
    uid: 965ec734-651a-416a-89dd-b0e0bc962b2b
  spec:
    sourcePod: network-check-source-6f8b768455-8rz9j
    targetEndpoint: a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T07:15:12Z"
      message: 'load-balancer-api-external: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.371706ms
      message: 'load-balancer-api-external: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 7.915742ms
      message: 'load-balancer-api-external: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 5.004465ms
      message: 'load-balancer-api-external: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 12.462257ms
      message: 'load-balancer-api-external: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 5.017146ms
      message: 'load-balancer-api-external: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 8.441759ms
      message: 'load-balancer-api-external: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 4.802953ms
      message: 'load-balancer-api-external: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 6.514613ms
      message: 'load-balancer-api-external: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 4.648176ms
      message: 'load-balancer-api-external: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:23:12Z"
    - latency: 7.05161ms
      message: 'load-balancer-api-external: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:23:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:09:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-10-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-10.ec2.internal
      uid: 79564ff7-2106-4e74-8e20-4771af93f396
    resourceVersion: "19387"
    uid: a3d63b44-82d6-4799-9e29-07f2120412d5
  spec:
    sourcePod: network-check-source-6f8b768455-8rz9j
    targetEndpoint: a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T07:15:12Z"
      message: 'load-balancer-api-internal: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.408542ms
      message: 'load-balancer-api-internal: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 7.863199ms
      message: 'load-balancer-api-internal: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 4.415042ms
      message: 'load-balancer-api-internal: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 12.383997ms
      message: 'load-balancer-api-internal: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 5.04312ms
      message: 'load-balancer-api-internal: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 8.381457ms
      message: 'load-balancer-api-internal: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 4.600833ms
      message: 'load-balancer-api-internal: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 6.493804ms
      message: 'load-balancer-api-internal: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 4.650848ms
      message: 'load-balancer-api-internal: tcp connection to a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:23:12Z"
    - latency: 7.022541ms
      message: 'load-balancer-api-internal: resolved host name a18efc0fbf9094686b69aa1636ea97a8-911e0086810f62a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:23:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:09:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-10-to-network-check-target-ip-10-0-129-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-10.ec2.internal
      uid: 79564ff7-2106-4e74-8e20-4771af93f396
    resourceVersion: "20546"
    uid: d05027d9-a8aa-4923-96ed-86872f2319ca
  spec:
    sourcePod: network-check-source-6f8b768455-8rz9j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T07:16:12Z"
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 783.052µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:30:12Z"
    - latency: 1.180359ms
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:29:12Z"
    - latency: 766.858µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:28:12Z"
    - latency: 918.675µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 2.172177ms
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 696.418µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 976.954µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 918.266µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:23:12Z"
    - latency: 818.756µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:22:12Z"
    - latency: 800.198µs
      message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:09:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-10-to-network-check-target-ip-10-0-129-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-10.ec2.internal
      uid: 79564ff7-2106-4e74-8e20-4771af93f396
    resourceVersion: "20544"
    uid: 4da015c4-01b8-43cf-8c9c-8e23fa9eb12a
  spec:
    sourcePod: network-check-source-6f8b768455-8rz9j
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T07:16:12Z"
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.81899ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:30:12Z"
    - latency: 1.92486ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:29:12Z"
    - latency: 1.848315ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:28:12Z"
    - latency: 1.73038ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 2.235431ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 1.550713ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 1.493544ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 2.007644ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:23:12Z"
    - latency: 2.028723ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:22:12Z"
    - latency: 1.776248ms
      message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:09:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-10-to-network-check-target-ip-10-0-130-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-10.ec2.internal
      uid: 79564ff7-2106-4e74-8e20-4771af93f396
    resourceVersion: "20545"
    uid: 97d22ccb-6c38-4ef1-8b7e-fba97a96d449
  spec:
    sourcePod: network-check-source-6f8b768455-8rz9j
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T07:16:12Z"
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.055649ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:30:12Z"
    - latency: 2.078655ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:29:12Z"
    - latency: 1.962326ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:28:12Z"
    - latency: 1.996419ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 2.230105ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 2.228947ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 1.841873ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 2.078827ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:23:12Z"
    - latency: 2.077508ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:22:12Z"
    - latency: 2.14874ms
      message: 'network-check-target-ip-10-0-130-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:09:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-10-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-10.ec2.internal
      uid: 79564ff7-2106-4e74-8e20-4771af93f396
    resourceVersion: "19385"
    uid: 02101f0c-ec3c-4d5a-8ec5-86bc48068410
  spec:
    sourcePod: network-check-source-6f8b768455-8rz9j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T07:15:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 745.918µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 1.623752ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:27:12Z"
    - latency: 913.585µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 4.062978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:26:12Z"
    - latency: 762.702µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 1.723833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:25:12Z"
    - latency: 833.256µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 1.518737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:24:12Z"
    - latency: 810.204µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T07:23:12Z"
    - latency: 1.832377ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T07:23:12Z"
kind: List
metadata:
  resourceVersion: ""