apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T20:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-21.ec2.internal
      uid: 1d6b9a1b-767c-4b4f-befb-719ffe959c54
    resourceVersion: "77493"
    uid: 01708318-fa0d-4a31-87cc-de7cde2ce747
  spec:
    sourcePod: network-check-source-65bdbbff45-kshwx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T20:31:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.82µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:20:05Z"
    - latency: 1.442976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:19:05Z"
    - latency: 1.626025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 1.287328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 1.545224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 1.21577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 1.281862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:14:05Z"
    - latency: 1.550662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:13:05Z"
    - latency: 1.444504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:12:05Z"
    - latency: 958.476µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T20:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-21.ec2.internal
      uid: 1d6b9a1b-767c-4b4f-befb-719ffe959c54
    resourceVersion: "75583"
    uid: a4135df0-ba1f-44fd-9f97-07a497ef4d19
  spec:
    sourcePod: network-check-source-65bdbbff45-kshwx
    targetEndpoint: aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T20:30:05Z"
      message: 'load-balancer-api-external: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.880947ms
      message: 'load-balancer-api-external: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 8.607157ms
      message: 'load-balancer-api-external: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 5.179606ms
      message: 'load-balancer-api-external: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 9.064267ms
      message: 'load-balancer-api-external: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 5.682713ms
      message: 'load-balancer-api-external: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 8.827577ms
      message: 'load-balancer-api-external: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 5.088452ms
      message: 'load-balancer-api-external: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 9.413426ms
      message: 'load-balancer-api-external: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 5.462614ms
      message: 'load-balancer-api-external: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:14:05Z"
    - latency: 13.666256ms
      message: 'load-balancer-api-external: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T20:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-21.ec2.internal
      uid: 1d6b9a1b-767c-4b4f-befb-719ffe959c54
    resourceVersion: "75584"
    uid: bfbd88f4-0595-4169-bf64-8c36b36d7157
  spec:
    sourcePod: network-check-source-65bdbbff45-kshwx
    targetEndpoint: aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T20:30:05Z"
      message: 'load-balancer-api-internal: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.023086ms
      message: 'load-balancer-api-internal: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 8.395354ms
      message: 'load-balancer-api-internal: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 5.205305ms
      message: 'load-balancer-api-internal: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 9.105679ms
      message: 'load-balancer-api-internal: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 5.691956ms
      message: 'load-balancer-api-internal: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 8.737528ms
      message: 'load-balancer-api-internal: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 5.09605ms
      message: 'load-balancer-api-internal: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 9.365167ms
      message: 'load-balancer-api-internal: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 5.486028ms
      message: 'load-balancer-api-internal: tcp connection to aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:14:05Z"
    - latency: 13.433108ms
      message: 'load-balancer-api-internal: resolved host name aaae279dc2a2c4b629d1a0029743209e-6de31e04dc04e292.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T20:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-21-to-network-check-target-ip-10-0-131-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-21.ec2.internal
      uid: 1d6b9a1b-767c-4b4f-befb-719ffe959c54
    resourceVersion: "77491"
    uid: bdfdddbb-c9fb-4ca0-9abe-9f3527d52f61
  spec:
    sourcePod: network-check-source-65bdbbff45-kshwx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T20:31:05Z"
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.153567ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:20:05Z"
    - latency: 2.269332ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:19:05Z"
    - latency: 2.275671ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 2.345097ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 2.421102ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 2.339591ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 2.243749ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:14:05Z"
    - latency: 2.063227ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:13:05Z"
    - latency: 2.449976ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:12:05Z"
    - latency: 2.181828ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T20:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-21-to-network-check-target-ip-10-0-140-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-21.ec2.internal
      uid: 1d6b9a1b-767c-4b4f-befb-719ffe959c54
    resourceVersion: "77490"
    uid: f23a90c8-17e8-4cc3-91d3-7bcfe26997e3
  spec:
    sourcePod: network-check-source-65bdbbff45-kshwx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T20:31:05Z"
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.054217ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:20:05Z"
    - latency: 1.541081ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:19:05Z"
    - latency: 1.053849ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 847.786µs
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 1.87138ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 917.987µs
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 1.43213ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:14:05Z"
    - latency: 1.235331ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:13:05Z"
    - latency: 1.299528ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:12:05Z"
    - latency: 1.302774ms
      message: 'network-check-target-ip-10-0-140-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T20:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-21-to-network-check-target-ip-10-0-142-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-21.ec2.internal
      uid: 1d6b9a1b-767c-4b4f-befb-719ffe959c54
    resourceVersion: "77492"
    uid: 464ad7af-9ee2-4d3d-bc0e-f1a2f2406008
  spec:
    sourcePod: network-check-source-65bdbbff45-kshwx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T20:31:05Z"
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.19814ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:20:05Z"
    - latency: 2.397801ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:19:05Z"
    - latency: 2.413864ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 2.417688ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 2.411892ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 2.326771ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 2.150026ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:14:05Z"
    - latency: 2.410844ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:13:05Z"
    - latency: 2.30386ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:12:05Z"
    - latency: 2.162864ms
      message: 'network-check-target-ip-10-0-142-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T20:24:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-21.ec2.internal
      uid: 1d6b9a1b-767c-4b4f-befb-719ffe959c54
    resourceVersion: "75582"
    uid: f02de37f-82ff-4cee-b54f-e08f1d19a509
  spec:
    sourcePod: network-check-source-65bdbbff45-kshwx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T20:30:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.896µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 1.899586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:18:05Z"
    - latency: 1.212264ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 1.861337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:17:05Z"
    - latency: 1.031935ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 1.868598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:16:05Z"
    - latency: 1.032078ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 1.995234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:15:05Z"
    - latency: 932.757µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T21:14:05Z"
    - latency: 2.115088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T21:14:05Z"
kind: List
metadata:
  resourceVersion: ""