apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-18-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-18.us-west-1.compute.internal
      uid: 875bbc5f-c45d-48ce-99b7-013d92b38a7c
    resourceVersion: "43278"
    uid: cb1ff386-8adf-4105-a849-2d51291d774c
  spec:
    sourcePod: network-check-source-6f78d59f99-8hlvs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:43:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.423743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 956.35µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:18Z"
    - latency: 3.433153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:55:18Z"
    - latency: 1.217382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:54:18Z"
    - latency: 965.627µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:53:18Z"
    - latency: 1.335102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:18Z"
    - latency: 1.4304ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:18Z"
    - latency: 1.300916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:18Z"
    - latency: 1.268777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:18Z"
    - latency: 1.168258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-18-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-18.us-west-1.compute.internal
      uid: 875bbc5f-c45d-48ce-99b7-013d92b38a7c
    resourceVersion: "48512"
    uid: ac9babde-ca11-4f03-bfab-c72cd6367f35
  spec:
    sourcePod: network-check-source-6f78d59f99-8hlvs
    targetEndpoint: aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:42:18Z"
      message: 'load-balancer-api-external: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.661074ms
      message: 'load-balancer-api-external: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:00:18Z"
    - latency: 3.407929ms
      message: 'load-balancer-api-external: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:00:18Z"
    - latency: 55.739981ms
      message: 'load-balancer-api-external: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:59:18Z"
    - latency: 1.860818ms
      message: 'load-balancer-api-external: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:59:18Z"
    - latency: 54.492618ms
      message: 'load-balancer-api-external: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:58:18Z"
    - latency: 3.287017ms
      message: 'load-balancer-api-external: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:58:18Z"
    - latency: 53.013509ms
      message: 'load-balancer-api-external: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 6.128781ms
      message: 'load-balancer-api-external: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 58.014401ms
      message: 'load-balancer-api-external: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:18Z"
    - latency: 2.92752ms
      message: 'load-balancer-api-external: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-18-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-18.us-west-1.compute.internal
      uid: 875bbc5f-c45d-48ce-99b7-013d92b38a7c
    resourceVersion: "48513"
    uid: 9994d426-1baf-4e0c-8972-2d884c29695f
  spec:
    sourcePod: network-check-source-6f78d59f99-8hlvs
    targetEndpoint: aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:42:18Z"
      message: 'load-balancer-api-internal: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.952374ms
      message: 'load-balancer-api-internal: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:00:18Z"
    - latency: 6.450662ms
      message: 'load-balancer-api-internal: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:00:18Z"
    - latency: 55.732384ms
      message: 'load-balancer-api-internal: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:59:18Z"
    - latency: 6.019901ms
      message: 'load-balancer-api-internal: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:59:18Z"
    - latency: 54.950794ms
      message: 'load-balancer-api-internal: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:58:18Z"
    - latency: 6.505613ms
      message: 'load-balancer-api-internal: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:58:18Z"
    - latency: 53.003462ms
      message: 'load-balancer-api-internal: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 8.770223ms
      message: 'load-balancer-api-internal: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 64.225857ms
      message: 'load-balancer-api-internal: tcp connection to aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:18Z"
    - latency: 6.161739ms
      message: 'load-balancer-api-internal: resolved host name aa64b852660404cf9a45925727badae8-e04a1860fe467e96.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-18-to-network-check-target-ip-10-0-129-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-18.us-west-1.compute.internal
      uid: 875bbc5f-c45d-48ce-99b7-013d92b38a7c
    resourceVersion: "43276"
    uid: 8b1ea57f-51bd-4306-b7dc-548ea83f52f1
  spec:
    sourcePod: network-check-source-6f78d59f99-8hlvs
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:43:18Z"
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.736387ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 1.904217ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:18Z"
    - latency: 4.349147ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:55:18Z"
    - latency: 2.1618ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:54:18Z"
    - latency: 1.935845ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:53:18Z"
    - latency: 2.448509ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:18Z"
    - latency: 2.473953ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:18Z"
    - latency: 2.123271ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:18Z"
    - latency: 2.482964ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:18Z"
    - latency: 2.267014ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-18-to-network-check-target-ip-10-0-135-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-18.us-west-1.compute.internal
      uid: 875bbc5f-c45d-48ce-99b7-013d92b38a7c
    resourceVersion: "43274"
    uid: 3ebc80d1-2ed8-4bf2-ba43-aedbd80463c4
  spec:
    sourcePod: network-check-source-6f78d59f99-8hlvs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:43:18Z"
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.563864ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 2.404752ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:18Z"
    - latency: 4.254159ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:55:18Z"
    - latency: 2.278059ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:54:18Z"
    - latency: 2.446839ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:53:18Z"
    - latency: 2.111471ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:18Z"
    - latency: 2.795872ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:18Z"
    - latency: 2.26553ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:18Z"
    - latency: 2.450727ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:18Z"
    - latency: 2.379655ms
      message: 'network-check-target-ip-10-0-135-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-18-to-network-check-target-ip-10-0-140-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-18.us-west-1.compute.internal
      uid: 875bbc5f-c45d-48ce-99b7-013d92b38a7c
    resourceVersion: "43273"
    uid: 7c56815a-9077-4222-ba9a-0aa99b23b27b
  spec:
    sourcePod: network-check-source-6f78d59f99-8hlvs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:43:18Z"
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.682502ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 1.098941ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:18Z"
    - latency: 5.614181ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:55:18Z"
    - latency: 1.450203ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:54:18Z"
    - latency: 972.808µs
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:53:18Z"
    - latency: 1.249071ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:18Z"
    - latency: 1.191152ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:18Z"
    - latency: 966.985µs
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:18Z"
    - latency: 1.099427ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:18Z"
    - latency: 1.54172ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:36:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-18-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-18.us-west-1.compute.internal
      uid: 875bbc5f-c45d-48ce-99b7-013d92b38a7c
    resourceVersion: "48509"
    uid: c8e8cc9a-6455-45f5-ba52-50022f4732e3
  spec:
    sourcePod: network-check-source-6f78d59f99-8hlvs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:42:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.263µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:00:18Z"
    - latency: 2.020598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:00:18Z"
    - latency: 937.298µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:59:18Z"
    - latency: 1.620503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:59:18Z"
    - latency: 1.10329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:58:18Z"
    - latency: 2.501039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:58:18Z"
    - latency: 1.311573ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 2.131291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:57:18Z"
    - latency: 1.307962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:18Z"
    - latency: 2.002991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:56:18Z"
kind: List
metadata:
  resourceVersion: ""