apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T16:36:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-170-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-170.ec2.internal
      uid: b431ddc1-f452-4484-bd2d-897e33004645
    resourceVersion: "56308"
    uid: c649cf3b-19c1-4706-a271-81ad3361ceda
  spec:
    sourcePod: network-check-source-989f8b8dc-5rxck
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T16:43:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.046684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 1.031719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 1.351363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 951.476µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:08:05Z"
    - latency: 1.436099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:07:05Z"
    - latency: 930.967µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:06:05Z"
    - latency: 1.075136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:05:05Z"
    - latency: 1.208058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:04:05Z"
    - latency: 1.048163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:03:05Z"
    - latency: 981.667µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T16:36:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-170-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-170.ec2.internal
      uid: b431ddc1-f452-4484-bd2d-897e33004645
    resourceVersion: "57124"
    uid: 35df604f-d51c-4892-a2f9-aafe4c6d8837
  spec:
    sourcePod: network-check-source-989f8b8dc-5rxck
    targetEndpoint: a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T16:42:05Z"
      message: 'load-balancer-api-external: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.340216ms
      message: 'load-balancer-api-external: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:12:05Z"
    - latency: 7.293068ms
      message: 'load-balancer-api-external: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:12:05Z"
    - latency: 5.56802ms
      message: 'load-balancer-api-external: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 11.11575ms
      message: 'load-balancer-api-external: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 5.914951ms
      message: 'load-balancer-api-external: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 7.35187ms
      message: 'load-balancer-api-external: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 5.421214ms
      message: 'load-balancer-api-external: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 8.524252ms
      message: 'load-balancer-api-external: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 6.173415ms
      message: 'load-balancer-api-external: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:08:05Z"
    - latency: 7.151005ms
      message: 'load-balancer-api-external: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T16:36:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-170-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-170.ec2.internal
      uid: b431ddc1-f452-4484-bd2d-897e33004645
    resourceVersion: "57123"
    uid: 34bb3702-224f-4013-a28c-9bd6da1cc93a
  spec:
    sourcePod: network-check-source-989f8b8dc-5rxck
    targetEndpoint: a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T16:42:05Z"
      message: 'load-balancer-api-internal: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.353601ms
      message: 'load-balancer-api-internal: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:12:05Z"
    - latency: 7.240064ms
      message: 'load-balancer-api-internal: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:12:05Z"
    - latency: 5.599526ms
      message: 'load-balancer-api-internal: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 11.086404ms
      message: 'load-balancer-api-internal: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 5.949828ms
      message: 'load-balancer-api-internal: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 7.282211ms
      message: 'load-balancer-api-internal: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 5.930334ms
      message: 'load-balancer-api-internal: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 8.303308ms
      message: 'load-balancer-api-internal: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 6.152176ms
      message: 'load-balancer-api-internal: tcp connection to a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:08:05Z"
    - latency: 7.179582ms
      message: 'load-balancer-api-internal: resolved host name a5ffe28cee21d4261bef4bd943b56f4a-f07182f10c46170e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T16:36:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-170-to-network-check-target-ip-10-0-138-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-170.ec2.internal
      uid: b431ddc1-f452-4484-bd2d-897e33004645
    resourceVersion: "56305"
    uid: 9850dd9b-c195-4277-949e-570a8bd6ceb4
  spec:
    sourcePod: network-check-source-989f8b8dc-5rxck
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T16:43:05Z"
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.428639ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 846.455µs
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 1.600962ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 951.796µs
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:08:05Z"
    - latency: 852.972µs
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:07:05Z"
    - latency: 1.265808ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:06:05Z"
    - latency: 1.267455ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:05:05Z"
    - latency: 796.735µs
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:04:05Z"
    - latency: 1.538734ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:03:05Z"
    - latency: 852.103µs
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T16:36:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-170-to-network-check-target-ip-10-0-140-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-170.ec2.internal
      uid: b431ddc1-f452-4484-bd2d-897e33004645
    resourceVersion: "56307"
    uid: 37120a14-32ab-41d6-96db-a27abd45aa74
  spec:
    sourcePod: network-check-source-989f8b8dc-5rxck
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T16:43:05Z"
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.72265ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 2.385728ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 2.479707ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 2.649315ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:08:05Z"
    - latency: 2.156819ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:07:05Z"
    - latency: 2.228755ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:06:05Z"
    - latency: 2.202502ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:05:05Z"
    - latency: 2.628943ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:04:05Z"
    - latency: 2.447993ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:03:05Z"
    - latency: 2.308511ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T16:36:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-170-to-network-check-target-ip-10-0-142-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-170.ec2.internal
      uid: b431ddc1-f452-4484-bd2d-897e33004645
    resourceVersion: "56306"
    uid: 3d188cb2-822d-498a-b96e-879ed162bed4
  spec:
    sourcePod: network-check-source-989f8b8dc-5rxck
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T16:43:05Z"
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.405462ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 2.717ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 3.316763ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 2.547377ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:08:05Z"
    - latency: 3.058231ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:07:05Z"
    - latency: 2.232781ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:06:05Z"
    - latency: 2.37311ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:05:05Z"
    - latency: 2.559153ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:04:05Z"
    - latency: 2.394172ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:03:05Z"
    - latency: 2.401639ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T16:36:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-170-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-170.ec2.internal
      uid: b431ddc1-f452-4484-bd2d-897e33004645
    resourceVersion: "57122"
    uid: 1612a14c-b500-4b8f-acd4-f745da6199bc
  spec:
    sourcePod: network-check-source-989f8b8dc-5rxck
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T16:42:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.594µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:12:05Z"
    - latency: 1.775873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:12:05Z"
    - latency: 1.270505ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 1.840355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:11:05Z"
    - latency: 766.659µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 1.90418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:10:05Z"
    - latency: 980.613µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 2.437618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:09:05Z"
    - latency: 1.008346ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T17:08:05Z"
    - latency: 1.953573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T17:08:05Z"
kind: List
metadata:
  resourceVersion: ""