apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-55.ec2.internal
      uid: a273616b-99f5-48ad-afa4-d3c141f23e37
    resourceVersion: "20201"
    uid: a4b493a1-71ce-4363-9686-8f6aa3af2f65
  spec:
    sourcePod: network-check-source-685456655f-6g56h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:18:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.425954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:32:24Z"
    - latency: 899.287µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:31:24Z"
    - latency: 937.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:30:24Z"
    - latency: 960.362µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 990.037µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 1.002412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 945.239µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 1.071259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:24Z"
    - latency: 1.080968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:24Z"
    - latency: 996.995µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-55.ec2.internal
      uid: a273616b-99f5-48ad-afa4-d3c141f23e37
    resourceVersion: "19058"
    uid: c8173086-918d-4b69-8ba8-d92908ac1bc8
  spec:
    sourcePod: network-check-source-685456655f-6g56h
    targetEndpoint: a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:17:24Z"
      message: 'load-balancer-api-external: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.007273ms
      message: 'load-balancer-api-external: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 6.749174ms
      message: 'load-balancer-api-external: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 3.718002ms
      message: 'load-balancer-api-external: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 7.223161ms
      message: 'load-balancer-api-external: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 4.425454ms
      message: 'load-balancer-api-external: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 6.575767ms
      message: 'load-balancer-api-external: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 3.948455ms
      message: 'load-balancer-api-external: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 7.470431ms
      message: 'load-balancer-api-external: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 4.866759ms
      message: 'load-balancer-api-external: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:24Z"
    - latency: 7.75075ms
      message: 'load-balancer-api-external: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:25:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-55.ec2.internal
      uid: a273616b-99f5-48ad-afa4-d3c141f23e37
    resourceVersion: "19057"
    uid: a4b2073a-6c4b-46ce-96f9-5187fde9f570
  spec:
    sourcePod: network-check-source-685456655f-6g56h
    targetEndpoint: a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:17:24Z"
      message: 'load-balancer-api-internal: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.047724ms
      message: 'load-balancer-api-internal: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 6.660769ms
      message: 'load-balancer-api-internal: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 5.186769ms
      message: 'load-balancer-api-internal: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 7.173875ms
      message: 'load-balancer-api-internal: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 4.427908ms
      message: 'load-balancer-api-internal: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 6.497442ms
      message: 'load-balancer-api-internal: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 3.380592ms
      message: 'load-balancer-api-internal: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 7.383247ms
      message: 'load-balancer-api-internal: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 4.807494ms
      message: 'load-balancer-api-internal: tcp connection to a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:24Z"
    - latency: 7.909091ms
      message: 'load-balancer-api-internal: resolved host name a748cd0c103f74c77a4bf0040441890a-6c768dad8b355efe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:25:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-130-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-55.ec2.internal
      uid: a273616b-99f5-48ad-afa4-d3c141f23e37
    resourceVersion: "20199"
    uid: 03ccd9cd-ce67-4252-8006-bb1a04b84b8b
  spec:
    sourcePod: network-check-source-685456655f-6g56h
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:18:24Z"
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.169338ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:32:24Z"
    - latency: 838.318µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:31:24Z"
    - latency: 957.543µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:30:24Z"
    - latency: 874.673µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 1.187896ms
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 921.738µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 952.66µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 977.959µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:24Z"
    - latency: 915.596µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:24Z"
    - latency: 800.885µs
      message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-140-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-55.ec2.internal
      uid: a273616b-99f5-48ad-afa4-d3c141f23e37
    resourceVersion: "20200"
    uid: 3c9611d7-ea59-4f28-b818-9caddd4dec7c
  spec:
    sourcePod: network-check-source-685456655f-6g56h
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:18:24Z"
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.122972ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:32:24Z"
    - latency: 2.441663ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:31:24Z"
    - latency: 2.303716ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:30:24Z"
    - latency: 2.192216ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 2.26589ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 2.171146ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 2.235981ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 2.133478ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:24Z"
    - latency: 2.393601ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:24Z"
    - latency: 2.284947ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-55-to-network-check-target-ip-10-0-143-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-55.ec2.internal
      uid: a273616b-99f5-48ad-afa4-d3c141f23e37
    resourceVersion: "20198"
    uid: 967895b5-69d9-4274-a8ac-97aa86eef223
  spec:
    sourcePod: network-check-source-685456655f-6g56h
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:18:24Z"
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.5942ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:32:24Z"
    - latency: 2.007129ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:31:24Z"
    - latency: 2.449609ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:30:24Z"
    - latency: 2.351144ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 2.26076ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 2.076299ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 2.461262ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 2.435523ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:24Z"
    - latency: 2.36801ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:24Z"
    - latency: 2.24296ms
      message: 'network-check-target-ip-10-0-143-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:11:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-55.ec2.internal
      uid: a273616b-99f5-48ad-afa4-d3c141f23e37
    resourceVersion: "19056"
    uid: 4290b121-c68d-4547-a040-7d5ce469082a
  spec:
    sourcePod: network-check-source-685456655f-6g56h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:17:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 731.218µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 1.718864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:29:24Z"
    - latency: 816.977µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 1.863179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:28:24Z"
    - latency: 1.059976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 1.755237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:27:24Z"
    - latency: 1.396096ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 1.745355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:26:24Z"
    - latency: 935.987µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:24Z"
    - latency: 1.893152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:25:24Z"
kind: List
metadata:
  resourceVersion: ""