apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: 1ac7d9ec-5eac-4a0f-9bde-a56c1289e115
    resourceVersion: "23637"
    uid: 663b973b-28fa-463c-b16d-c6cfb11cb793
  spec:
    sourcePod: network-check-source-7cbc45fddc-cchl4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.152475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 1.465017ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:58Z"
    - latency: 1.590326ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:58Z"
    - latency: 1.147167ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:58Z"
    - latency: 1.219831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:58Z"
    - latency: 865.063µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:58Z"
    - latency: 928.072µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:58Z"
    - latency: 1.034704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:55:58Z"
    - latency: 1.330882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:54:58Z"
    - latency: 963.925µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:53:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: 1ac7d9ec-5eac-4a0f-9bde-a56c1289e115
    resourceVersion: "25056"
    uid: 6a62381d-cdcd-45ff-87ee-e3175a83c312
  spec:
    sourcePod: network-check-source-7cbc45fddc-cchl4
    targetEndpoint: a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:58Z"
      message: 'load-balancer-api-external: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.751529ms
      message: 'load-balancer-api-external: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:58Z"
    - latency: 7.59518ms
      message: 'load-balancer-api-external: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:05:58Z"
    - latency: 6.842354ms
      message: 'load-balancer-api-external: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:58Z"
    - latency: 7.065976ms
      message: 'load-balancer-api-external: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:04:58Z"
    - latency: 4.84537ms
      message: 'load-balancer-api-external: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:58Z"
    - latency: 6.470037ms
      message: 'load-balancer-api-external: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:03:58Z"
    - latency: 5.073434ms
      message: 'load-balancer-api-external: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 7.253268ms
      message: 'load-balancer-api-external: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 4.242786ms
      message: 'load-balancer-api-external: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:58Z"
    - latency: 11.414639ms
      message: 'load-balancer-api-external: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:01:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: 1ac7d9ec-5eac-4a0f-9bde-a56c1289e115
    resourceVersion: "25057"
    uid: d8ec6a9a-32b2-444c-a079-8c5117c71b11
  spec:
    sourcePod: network-check-source-7cbc45fddc-cchl4
    targetEndpoint: a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:58Z"
      message: 'load-balancer-api-internal: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.57693ms
      message: 'load-balancer-api-internal: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:58Z"
    - latency: 7.54166ms
      message: 'load-balancer-api-internal: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:05:58Z"
    - latency: 5.286249ms
      message: 'load-balancer-api-internal: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:58Z"
    - latency: 7.120795ms
      message: 'load-balancer-api-internal: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:04:58Z"
    - latency: 4.608857ms
      message: 'load-balancer-api-internal: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:58Z"
    - latency: 6.57564ms
      message: 'load-balancer-api-internal: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:03:58Z"
    - latency: 5.090648ms
      message: 'load-balancer-api-internal: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 7.306203ms
      message: 'load-balancer-api-internal: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 4.686776ms
      message: 'load-balancer-api-internal: tcp connection to a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:58Z"
    - latency: 11.386271ms
      message: 'load-balancer-api-internal: resolved host name a38d827c26867415a91db529797da399-aa2f33587d936e11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:01:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-ip-10-0-134-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: 1ac7d9ec-5eac-4a0f-9bde-a56c1289e115
    resourceVersion: "23634"
    uid: b74bb4cf-44f8-4e51-b721-80280c2f0710
  spec:
    sourcePod: network-check-source-7cbc45fddc-cchl4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:58Z"
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.166957ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 1.766832ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:58Z"
    - latency: 1.054791ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:58Z"
    - latency: 978.787µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:58Z"
    - latency: 1.047609ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:58Z"
    - latency: 1.023861ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:58Z"
    - latency: 970.553µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:58Z"
    - latency: 993.078µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:55:58Z"
    - latency: 1.264833ms
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:54:58Z"
    - latency: 954.855µs
      message: 'network-check-target-ip-10-0-134-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:53:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-ip-10-0-135-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: 1ac7d9ec-5eac-4a0f-9bde-a56c1289e115
    resourceVersion: "23636"
    uid: 0de96fbf-8ad4-468b-93a8-9f36cafcf09b
  spec:
    sourcePod: network-check-source-7cbc45fddc-cchl4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:58Z"
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.21316ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 2.244462ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:58Z"
    - latency: 1.982236ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:58Z"
    - latency: 2.224846ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:58Z"
    - latency: 2.15184ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:58Z"
    - latency: 2.059843ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:58Z"
    - latency: 2.067942ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:58Z"
    - latency: 2.250518ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:55:58Z"
    - latency: 2.103693ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:54:58Z"
    - latency: 2.127397ms
      message: 'network-check-target-ip-10-0-135-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:53:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-ip-10-0-142-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: 1ac7d9ec-5eac-4a0f-9bde-a56c1289e115
    resourceVersion: "23635"
    uid: e004a78d-bd80-44df-b659-e2f589b2a206
  spec:
    sourcePod: network-check-source-7cbc45fddc-cchl4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:48:58Z"
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221091ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 2.425147ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:58Z"
    - latency: 1.902585ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:00:58Z"
    - latency: 2.201165ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:59:58Z"
    - latency: 2.174175ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:58:58Z"
    - latency: 2.236612ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:57:58Z"
    - latency: 2.1701ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:56:58Z"
    - latency: 2.200639ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:55:58Z"
    - latency: 2.119577ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:54:58Z"
    - latency: 2.220085ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:53:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:41:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-49-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-49.ec2.internal
      uid: 1ac7d9ec-5eac-4a0f-9bde-a56c1289e115
    resourceVersion: "25055"
    uid: 0eabf4b0-a035-464c-881b-ff9e7290d691
  spec:
    sourcePod: network-check-source-7cbc45fddc-cchl4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044485ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:58Z"
    - latency: 1.647305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:05:58Z"
    - latency: 971.726µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:58Z"
    - latency: 1.818429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:04:58Z"
    - latency: 1.141531ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:58Z"
    - latency: 2.005698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:03:58Z"
    - latency: 1.147328ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 2.080725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:02:58Z"
    - latency: 1.060419ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:58Z"
    - latency: 2.124311ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:01:58Z"
kind: List
metadata:
  resourceVersion: ""