apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T05:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-253.us-west-1.compute.internal
      uid: 637352f9-70e8-4f4a-be08-23beeb798094
    resourceVersion: "129594"
    uid: fa008723-28a0-4bc2-bd31-4aa5bbba3730
  spec:
    sourcePod: network-check-source-6f78d59f99-srv7d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T05:13:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.11277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 840.434µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 1.055822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 1.223988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:27:08Z"
    - latency: 1.050087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:26:08Z"
    - latency: 1.251253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:25:08Z"
    - latency: 1.248711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:24:08Z"
    - latency: 813.565µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:23:08Z"
    - latency: 1.005251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:22:08Z"
    - latency: 1.075694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:21:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T05:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-253.us-west-1.compute.internal
      uid: 637352f9-70e8-4f4a-be08-23beeb798094
    resourceVersion: "130293"
    uid: dda804fa-3290-4332-b4b6-59762cd9092d
  spec:
    sourcePod: network-check-source-6f78d59f99-srv7d
    targetEndpoint: aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T05:12:08Z"
      message: 'load-balancer-api-external: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.187465ms
      message: 'load-balancer-api-external: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:31:08Z"
    - latency: 3.743714ms
      message: 'load-balancer-api-external: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:31:08Z"
    - latency: 53.941341ms
      message: 'load-balancer-api-external: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 5.017341ms
      message: 'load-balancer-api-external: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 54.725945ms
      message: 'load-balancer-api-external: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 3.645603ms
      message: 'load-balancer-api-external: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 55.017412ms
      message: 'load-balancer-api-external: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 4.38244ms
      message: 'load-balancer-api-external: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 54.85382ms
      message: 'load-balancer-api-external: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:27:08Z"
    - latency: 5.578067ms
      message: 'load-balancer-api-external: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T05:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-253.us-west-1.compute.internal
      uid: 637352f9-70e8-4f4a-be08-23beeb798094
    resourceVersion: "130292"
    uid: 815b9c06-276f-4421-aa72-565f480b174c
  spec:
    sourcePod: network-check-source-6f78d59f99-srv7d
    targetEndpoint: aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T05:12:08Z"
      message: 'load-balancer-api-internal: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.142227ms
      message: 'load-balancer-api-internal: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:31:08Z"
    - latency: 6.157716ms
      message: 'load-balancer-api-internal: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:31:08Z"
    - latency: 70.984004ms
      message: 'load-balancer-api-internal: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 6.937947ms
      message: 'load-balancer-api-internal: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 54.682233ms
      message: 'load-balancer-api-internal: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 6.379961ms
      message: 'load-balancer-api-internal: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 55.009117ms
      message: 'load-balancer-api-internal: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 6.670443ms
      message: 'load-balancer-api-internal: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 54.842713ms
      message: 'load-balancer-api-internal: tcp connection to aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:27:08Z"
    - latency: 8.379214ms
      message: 'load-balancer-api-internal: resolved host name aa20f316a090d4ba282b8462800e02e0-246993faf7c49e49.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:27:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T05:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-253-to-network-check-target-ip-10-0-129-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-253.us-west-1.compute.internal
      uid: 637352f9-70e8-4f4a-be08-23beeb798094
    resourceVersion: "129592"
    uid: c5a52ee8-1c24-4e28-9aa7-3b086aa9f527
  spec:
    sourcePod: network-check-source-6f78d59f99-srv7d
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T05:13:08Z"
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.237314ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 2.447166ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 1.961445ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 2.000357ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:27:08Z"
    - latency: 2.050282ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:26:08Z"
    - latency: 2.244772ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:25:08Z"
    - latency: 1.928523ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:24:08Z"
    - latency: 2.50092ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:23:08Z"
    - latency: 1.978288ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:22:08Z"
    - latency: 2.166791ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:21:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T05:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-253-to-network-check-target-ip-10-0-134-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-253.us-west-1.compute.internal
      uid: 637352f9-70e8-4f4a-be08-23beeb798094
    resourceVersion: "129591"
    uid: 959e473b-f0e8-48e9-9a5c-f62f778878ad
  spec:
    sourcePod: network-check-source-6f78d59f99-srv7d
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T05:13:08Z"
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.376µs
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 1.579447ms
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 1.145075ms
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 1.452106ms
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:27:08Z"
    - latency: 1.180249ms
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:26:08Z"
    - latency: 1.656898ms
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:25:08Z"
    - latency: 902.135µs
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:24:08Z"
    - latency: 1.300815ms
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:23:08Z"
    - latency: 914.057µs
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:22:08Z"
    - latency: 977.978µs
      message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:21:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T05:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-253-to-network-check-target-ip-10-0-141-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-253.us-west-1.compute.internal
      uid: 637352f9-70e8-4f4a-be08-23beeb798094
    resourceVersion: "129593"
    uid: 17522eb9-fcf1-453f-a04a-70199a0408d8
  spec:
    sourcePod: network-check-source-6f78d59f99-srv7d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T05:13:08Z"
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.065972ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 2.110117ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 1.874662ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 1.826609ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:27:08Z"
    - latency: 2.095551ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:26:08Z"
    - latency: 2.081022ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:25:08Z"
    - latency: 1.989827ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:24:08Z"
    - latency: 2.403563ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:23:08Z"
    - latency: 1.883333ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:22:08Z"
    - latency: 2.202857ms
      message: 'network-check-target-ip-10-0-141-97: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:21:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T05:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-253.us-west-1.compute.internal
      uid: 637352f9-70e8-4f4a-be08-23beeb798094
    resourceVersion: "130290"
    uid: d23b9997-875a-468b-8037-a61e263bc0f0
  spec:
    sourcePod: network-check-source-6f78d59f99-srv7d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T05:12:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.597µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:31:08Z"
    - latency: 1.69132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:31:08Z"
    - latency: 871.947µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 1.76117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:30:08Z"
    - latency: 1.086854ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 2.297876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:29:08Z"
    - latency: 892.581µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 1.964199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:28:08Z"
    - latency: 945.943µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T06:27:08Z"
    - latency: 1.829649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T06:27:08Z"
kind: List
metadata:
  resourceVersion: ""