apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 58bbd526-16ab-4bd2-a317-c246be49b2d9
    resourceVersion: "61273"
    uid: 9683be7a-68cc-4dea-95da-4d95600a9656
  spec:
    sourcePod: network-check-source-685456655f-9w7vx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:43:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.260057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 1.129267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 851.234µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 1.181316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:45Z"
    - latency: 1.31625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:45Z"
    - latency: 1.004791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:45Z"
    - latency: 1.430631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:45Z"
    - latency: 1.385592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:45Z"
    - latency: 1.267621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:03:45Z"
    - latency: 1.232654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 58bbd526-16ab-4bd2-a317-c246be49b2d9
    resourceVersion: "61957"
    uid: 8198c301-9b30-4bdb-afc1-4000eb716346
  spec:
    sourcePod: network-check-source-685456655f-9w7vx
    targetEndpoint: af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:42:45Z"
      message: 'load-balancer-api-external: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.639788ms
      message: 'load-balancer-api-external: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:45Z"
    - latency: 10.608543ms
      message: 'load-balancer-api-external: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:12:45Z"
    - latency: 3.877682ms
      message: 'load-balancer-api-external: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 7.564618ms
      message: 'load-balancer-api-external: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 5.840725ms
      message: 'load-balancer-api-external: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 6.801977ms
      message: 'load-balancer-api-external: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 4.590762ms
      message: 'load-balancer-api-external: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 6.11054ms
      message: 'load-balancer-api-external: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 3.84994ms
      message: 'load-balancer-api-external: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:45Z"
    - latency: 7.008878ms
      message: 'load-balancer-api-external: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:08:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 58bbd526-16ab-4bd2-a317-c246be49b2d9
    resourceVersion: "61958"
    uid: 8a0ae1aa-5079-4cef-a5c9-8a16e6bfc4c8
  spec:
    sourcePod: network-check-source-685456655f-9w7vx
    targetEndpoint: af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:42:45Z"
      message: 'load-balancer-api-internal: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.651847ms
      message: 'load-balancer-api-internal: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:45Z"
    - latency: 10.575384ms
      message: 'load-balancer-api-internal: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:12:45Z"
    - latency: 3.855749ms
      message: 'load-balancer-api-internal: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 7.68041ms
      message: 'load-balancer-api-internal: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 5.822016ms
      message: 'load-balancer-api-internal: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 6.898587ms
      message: 'load-balancer-api-internal: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 4.679517ms
      message: 'load-balancer-api-internal: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 6.181904ms
      message: 'load-balancer-api-internal: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 4.119693ms
      message: 'load-balancer-api-internal: tcp connection to af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:45Z"
    - latency: 7.09665ms
      message: 'load-balancer-api-internal: resolved host name af183e95580a24186a1a3a34b57ec90b-5b8394b87caeaa80.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:08:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-ip-10-0-128-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 58bbd526-16ab-4bd2-a317-c246be49b2d9
    resourceVersion: "61270"
    uid: 8570212c-510d-491d-ae03-47530b26bb6d
  spec:
    sourcePod: network-check-source-685456655f-9w7vx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:43:45Z"
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.066654ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 1.922433ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 1.973101ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 2.267804ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:45Z"
    - latency: 2.413854ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:45Z"
    - latency: 2.354668ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:45Z"
    - latency: 2.883047ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:45Z"
    - latency: 2.722027ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:45Z"
    - latency: 2.223252ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:03:45Z"
    - latency: 2.761923ms
      message: 'network-check-target-ip-10-0-128-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-ip-10-0-133-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 58bbd526-16ab-4bd2-a317-c246be49b2d9
    resourceVersion: "61271"
    uid: e3df16d5-6ace-4f0b-8498-76981a8aa698
  spec:
    sourcePod: network-check-source-685456655f-9w7vx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:43:45Z"
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.532µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 976.652µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 1.630357ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 972.302µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:45Z"
    - latency: 975µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:45Z"
    - latency: 1.304401ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:45Z"
    - latency: 1.001298ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:45Z"
    - latency: 966.255µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:45Z"
    - latency: 990.934µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:03:45Z"
    - latency: 915.737µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-ip-10-0-140-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 58bbd526-16ab-4bd2-a317-c246be49b2d9
    resourceVersion: "61272"
    uid: e556b451-0c1b-4fd0-82aa-9bd81133ed66
  spec:
    sourcePod: network-check-source-685456655f-9w7vx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:43:45Z"
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.062895ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 2.071023ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 2.409184ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 2.101473ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:45Z"
    - latency: 2.445606ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:45Z"
    - latency: 2.391265ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:45Z"
    - latency: 2.757818ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:45Z"
    - latency: 2.137727ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:45Z"
    - latency: 2.223896ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:03:45Z"
    - latency: 2.372885ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:02:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:36:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 58bbd526-16ab-4bd2-a317-c246be49b2d9
    resourceVersion: "61956"
    uid: 8c51df57-6be8-4a6c-b306-6c6b6bc39663
  spec:
    sourcePod: network-check-source-685456655f-9w7vx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:42:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.41µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:45Z"
    - latency: 1.876023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:12:45Z"
    - latency: 1.020335ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 2.164892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:11:45Z"
    - latency: 1.104396ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 1.74392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:10:45Z"
    - latency: 967.33µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 1.637274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:09:45Z"
    - latency: 896.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:45Z"
    - latency: 1.959787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:08:45Z"
kind: List
metadata:
  resourceVersion: ""