apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:24:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: f0342412-182e-4e10-8c4a-ef4af5b65f79
    resourceVersion: "51779"
    uid: 9405bb9f-e41f-4b88-8327-1fde4a5f8463
  spec:
    sourcePod: network-check-source-685456655f-9zr8q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:31:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.728638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 1.192198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 1.181641ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:50:54Z"
    - latency: 1.46061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:49:54Z"
    - latency: 1.668956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:48:54Z"
    - latency: 1.201623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:54Z"
    - latency: 979.97µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:54Z"
    - latency: 968.042µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:54Z"
    - latency: 1.38387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:54Z"
    - latency: 1.081481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:24:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: f0342412-182e-4e10-8c4a-ef4af5b65f79
    resourceVersion: "53258"
    uid: 5737e845-ff96-4371-922d-4d281b51aeff
  spec:
    sourcePod: network-check-source-685456655f-9zr8q
    targetEndpoint: a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:30:54Z"
      message: 'load-balancer-api-external: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.495419ms
      message: 'load-balancer-api-external: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:54:54Z"
    - latency: 10.788662ms
      message: 'load-balancer-api-external: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:54:54Z"
    - latency: 3.657811ms
      message: 'load-balancer-api-external: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:53:54Z"
    - latency: 10.152761ms
      message: 'load-balancer-api-external: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:53:54Z"
    - latency: 5.961972ms
      message: 'load-balancer-api-external: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 8.731453ms
      message: 'load-balancer-api-external: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 5.749389ms
      message: 'load-balancer-api-external: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 8.577239ms
      message: 'load-balancer-api-external: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 5.580914ms
      message: 'load-balancer-api-external: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:50:54Z"
    - latency: 7.708538ms
      message: 'load-balancer-api-external: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:50:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:24:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: f0342412-182e-4e10-8c4a-ef4af5b65f79
    resourceVersion: "53257"
    uid: 4b6e3370-0a6e-4661-b93a-abbf63cbd443
  spec:
    sourcePod: network-check-source-685456655f-9zr8q
    targetEndpoint: a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:30:54Z"
      message: 'load-balancer-api-internal: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.467738ms
      message: 'load-balancer-api-internal: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:54:54Z"
    - latency: 10.722332ms
      message: 'load-balancer-api-internal: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:54:54Z"
    - latency: 3.665773ms
      message: 'load-balancer-api-internal: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:53:54Z"
    - latency: 10.091333ms
      message: 'load-balancer-api-internal: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:53:54Z"
    - latency: 6.69891ms
      message: 'load-balancer-api-internal: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 8.629955ms
      message: 'load-balancer-api-internal: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 5.716412ms
      message: 'load-balancer-api-internal: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 8.560239ms
      message: 'load-balancer-api-internal: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 5.58465ms
      message: 'load-balancer-api-internal: tcp connection to a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:50:54Z"
    - latency: 7.681769ms
      message: 'load-balancer-api-internal: resolved host name a2b5abacce68d4fc491c2baa534ddcf8-6dc40772eb109a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:50:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:24:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-135-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: f0342412-182e-4e10-8c4a-ef4af5b65f79
    resourceVersion: "51778"
    uid: 2d648354-2a70-4cac-b543-cdbee3c48df4
  spec:
    sourcePod: network-check-source-685456655f-9zr8q
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:31:54Z"
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.731844ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 2.529313ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 1.888514ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:50:54Z"
    - latency: 2.747121ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:49:54Z"
    - latency: 2.348628ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:48:54Z"
    - latency: 2.599989ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:54Z"
    - latency: 2.268468ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:54Z"
    - latency: 2.227036ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:54Z"
    - latency: 2.470279ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:54Z"
    - latency: 2.588856ms
      message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:24:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-138-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: f0342412-182e-4e10-8c4a-ef4af5b65f79
    resourceVersion: "51777"
    uid: 95c9f138-2b39-443e-82ac-52f90aedd623
  spec:
    sourcePod: network-check-source-685456655f-9zr8q
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:31:54Z"
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.569976ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 2.499901ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 2.243513ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:50:54Z"
    - latency: 2.622752ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:49:54Z"
    - latency: 2.58288ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:48:54Z"
    - latency: 2.546029ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:54Z"
    - latency: 2.196646ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:54Z"
    - latency: 2.069981ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:54Z"
    - latency: 2.556651ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:54Z"
    - latency: 2.511314ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:24:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-142-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: f0342412-182e-4e10-8c4a-ef4af5b65f79
    resourceVersion: "51776"
    uid: 781cd467-d132-411c-a44b-501e56825afe
  spec:
    sourcePod: network-check-source-685456655f-9zr8q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:31:54Z"
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 783.053µs
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 996.325µs
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 1.084014ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:50:54Z"
    - latency: 1.150271ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:49:54Z"
    - latency: 1.105339ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:48:54Z"
    - latency: 1.423984ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:54Z"
    - latency: 1.276627ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:54Z"
    - latency: 1.119153ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:54Z"
    - latency: 1.850522ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:54Z"
    - latency: 1.690865ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:24:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: f0342412-182e-4e10-8c4a-ef4af5b65f79
    resourceVersion: "53256"
    uid: 5698763b-4155-4f9f-9505-2a75d19e7534
  spec:
    sourcePod: network-check-source-685456655f-9zr8q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:30:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090432ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:54:54Z"
    - latency: 1.994783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:54:54Z"
    - latency: 809.03µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:53:54Z"
    - latency: 2.429043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:53:54Z"
    - latency: 1.183683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 2.369052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:52:54Z"
    - latency: 936.505µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 1.948103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:51:54Z"
    - latency: 1.289917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:50:54Z"
    - latency: 1.871537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:50:54Z"
kind: List
metadata:
  resourceVersion: ""