apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T21:19:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-92-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-92.ec2.internal
      uid: 730c88c8-1ff1-4608-9b26-958bb276feae
    resourceVersion: "32484"
    uid: 39f3625c-885c-4745-a8c0-131a7cb09f75
  spec:
    sourcePod: network-check-source-dbd9cf844-spkjk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T21:26:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.100579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:33:52Z"
    - latency: 889.286µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:32:52Z"
    - latency: 815.181µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:31:52Z"
    - latency: 946.131µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:30:52Z"
    - latency: 1.129674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:29:52Z"
    - latency: 2.500281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:28:52Z"
    - latency: 899.351µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:27:52Z"
    - latency: 883.005µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:26:52Z"
    - latency: 924.852µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:25:52Z"
    - latency: 926.546µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:24:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T21:19:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-92-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-92.ec2.internal
      uid: 730c88c8-1ff1-4608-9b26-958bb276feae
    resourceVersion: "36029"
    uid: 96ceaf3f-b53c-4fc0-8019-9202e69b3fa3
  spec:
    sourcePod: network-check-source-dbd9cf844-spkjk
    targetEndpoint: a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T21:25:52Z"
      message: 'load-balancer-api-external: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.307137ms
      message: 'load-balancer-api-external: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:37:52Z"
    - latency: 12.914463ms
      message: 'load-balancer-api-external: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:37:52Z"
    - latency: 4.368589ms
      message: 'load-balancer-api-external: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:36:52Z"
    - latency: 7.072916ms
      message: 'load-balancer-api-external: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:36:52Z"
    - latency: 5.189556ms
      message: 'load-balancer-api-external: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:35:52Z"
    - latency: 7.74071ms
      message: 'load-balancer-api-external: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:35:52Z"
    - latency: 5.306069ms
      message: 'load-balancer-api-external: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:34:52Z"
    - latency: 8.947023ms
      message: 'load-balancer-api-external: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:34:52Z"
    - latency: 4.673249ms
      message: 'load-balancer-api-external: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:33:52Z"
    - latency: 8.015191ms
      message: 'load-balancer-api-external: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:33:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T21:19:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-92-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-92.ec2.internal
      uid: 730c88c8-1ff1-4608-9b26-958bb276feae
    resourceVersion: "36028"
    uid: d83e6d7d-8649-408a-8b21-276840804c76
  spec:
    sourcePod: network-check-source-dbd9cf844-spkjk
    targetEndpoint: a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T21:25:52Z"
      message: 'load-balancer-api-internal: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.332426ms
      message: 'load-balancer-api-internal: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:37:52Z"
    - latency: 13.01112ms
      message: 'load-balancer-api-internal: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:37:52Z"
    - latency: 4.382605ms
      message: 'load-balancer-api-internal: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:36:52Z"
    - latency: 7.189111ms
      message: 'load-balancer-api-internal: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:36:52Z"
    - latency: 5.184454ms
      message: 'load-balancer-api-internal: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:35:52Z"
    - latency: 7.780542ms
      message: 'load-balancer-api-internal: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:35:52Z"
    - latency: 5.311756ms
      message: 'load-balancer-api-internal: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:34:52Z"
    - latency: 9.024077ms
      message: 'load-balancer-api-internal: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:34:52Z"
    - latency: 6.739314ms
      message: 'load-balancer-api-internal: tcp connection to a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:33:52Z"
    - latency: 8.087198ms
      message: 'load-balancer-api-internal: resolved host name a092c340001084bf186c327c475eab8e-124d02cd2388af90.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:33:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T21:19:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-92-to-network-check-target-ip-10-0-130-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-92.ec2.internal
      uid: 730c88c8-1ff1-4608-9b26-958bb276feae
    resourceVersion: "32481"
    uid: ab00b714-5b79-4602-a71e-d315963f2162
  spec:
    sourcePod: network-check-source-dbd9cf844-spkjk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T21:26:52Z"
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.791µs
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:33:52Z"
    - latency: 927.74µs
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:32:52Z"
    - latency: 969.993µs
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:31:52Z"
    - latency: 927.201µs
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:30:52Z"
    - latency: 1.481207ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:29:52Z"
    - latency: 893.02µs
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:28:52Z"
    - latency: 1.151339ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:27:52Z"
    - latency: 859.175µs
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:26:52Z"
    - latency: 1.187315ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:25:52Z"
    - latency: 973.894µs
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:24:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T21:19:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-92-to-network-check-target-ip-10-0-133-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-92.ec2.internal
      uid: 730c88c8-1ff1-4608-9b26-958bb276feae
    resourceVersion: "32482"
    uid: 8a12f526-458a-4ebf-b672-ec61cb366684
  spec:
    sourcePod: network-check-source-dbd9cf844-spkjk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T21:26:52Z"
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.433335ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:33:52Z"
    - latency: 2.381169ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:32:52Z"
    - latency: 2.38806ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:31:52Z"
    - latency: 2.131229ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:30:52Z"
    - latency: 2.606476ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:29:52Z"
    - latency: 3.975107ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:28:52Z"
    - latency: 2.249507ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:27:52Z"
    - latency: 2.197022ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:26:52Z"
    - latency: 2.297928ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:25:52Z"
    - latency: 2.271543ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:24:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T21:19:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-92-to-network-check-target-ip-10-0-135-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-92.ec2.internal
      uid: 730c88c8-1ff1-4608-9b26-958bb276feae
    resourceVersion: "32483"
    uid: da34aeb1-c367-4806-b4f8-b6c995510c93
  spec:
    sourcePod: network-check-source-dbd9cf844-spkjk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T21:26:52Z"
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.404996ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:33:52Z"
    - latency: 2.658872ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:32:52Z"
    - latency: 2.547608ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:31:52Z"
    - latency: 2.240769ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:30:52Z"
    - latency: 2.579385ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:29:52Z"
    - latency: 2.691095ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:28:52Z"
    - latency: 2.462479ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:27:52Z"
    - latency: 2.232746ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:26:52Z"
    - latency: 2.963492ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:25:52Z"
    - latency: 2.41587ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:24:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T21:19:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-92-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-92.ec2.internal
      uid: 730c88c8-1ff1-4608-9b26-958bb276feae
    resourceVersion: "36027"
    uid: d86f8b25-6e28-4d2e-ada1-6b6391dc9ab0
  spec:
    sourcePod: network-check-source-dbd9cf844-spkjk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T21:25:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:37:52Z"
    - latency: 1.962554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:37:52Z"
    - latency: 935.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:36:52Z"
    - latency: 1.698394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:36:52Z"
    - latency: 1.091543ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:35:52Z"
    - latency: 1.786732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:35:52Z"
    - latency: 1.252789ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:34:52Z"
    - latency: 1.875806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:34:52Z"
    - latency: 1.091947ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T21:33:52Z"
    - latency: 1.675853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T21:33:52Z"
kind: List
metadata:
  resourceVersion: ""