apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:22:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-117-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-117.ec2.internal
      uid: 36109df9-04b0-426a-9dbe-e917f63ab9da
    resourceVersion: "21355"
    uid: 88ed2c86-831a-442e-9d87-f790e2c0a680
  spec:
    sourcePod: network-check-source-7cbc45fddc-pcsdm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:29:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.507143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:43:59Z"
    - latency: 1.059451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:42:59Z"
    - latency: 919.906µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:41:59Z"
    - latency: 1.075862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 1.297926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 1.569744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 1.13103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 1.184983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:36:59Z"
    - latency: 1.118299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:35:59Z"
    - latency: 1.51268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:22:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-117-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-117.ec2.internal
      uid: 36109df9-04b0-426a-9dbe-e917f63ab9da
    resourceVersion: "20397"
    uid: a2206256-7386-4218-bb65-fbb0659d6051
  spec:
    sourcePod: network-check-source-7cbc45fddc-pcsdm
    targetEndpoint: a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:28:59Z"
      message: 'load-balancer-api-external: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.987823ms
      message: 'load-balancer-api-external: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 6.677208ms
      message: 'load-balancer-api-external: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 6.101495ms
      message: 'load-balancer-api-external: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 7.12847ms
      message: 'load-balancer-api-external: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 3.678392ms
      message: 'load-balancer-api-external: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 6.615933ms
      message: 'load-balancer-api-external: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 5.925062ms
      message: 'load-balancer-api-external: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 7.939597ms
      message: 'load-balancer-api-external: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 6.120449ms
      message: 'load-balancer-api-external: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:36:59Z"
    - latency: 6.839ms
      message: 'load-balancer-api-external: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:36:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:22:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-117-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-117.ec2.internal
      uid: 36109df9-04b0-426a-9dbe-e917f63ab9da
    resourceVersion: "20398"
    uid: eb1c9f18-445c-48eb-8caa-0cf50ae19a57
  spec:
    sourcePod: network-check-source-7cbc45fddc-pcsdm
    targetEndpoint: a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:28:59Z"
      message: 'load-balancer-api-internal: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.497013ms
      message: 'load-balancer-api-internal: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 6.746128ms
      message: 'load-balancer-api-internal: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 6.089962ms
      message: 'load-balancer-api-internal: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 7.161014ms
      message: 'load-balancer-api-internal: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 3.679619ms
      message: 'load-balancer-api-internal: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 6.721867ms
      message: 'load-balancer-api-internal: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 5.04498ms
      message: 'load-balancer-api-internal: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 7.906147ms
      message: 'load-balancer-api-internal: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 5.593617ms
      message: 'load-balancer-api-internal: tcp connection to a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:36:59Z"
    - latency: 6.816392ms
      message: 'load-balancer-api-internal: resolved host name a552b2525cc374d3fa91fa5e28bc33d5-5ea061c1e6864ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:36:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:22:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-117-to-network-check-target-ip-10-0-138-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-117.ec2.internal
      uid: 36109df9-04b0-426a-9dbe-e917f63ab9da
    resourceVersion: "21353"
    uid: 7ab4af8c-3df6-40b1-ae2b-8c7d52847eaf
  spec:
    sourcePod: network-check-source-7cbc45fddc-pcsdm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:29:59Z"
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.923605ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:43:59Z"
    - latency: 2.049116ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:42:59Z"
    - latency: 2.427795ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:41:59Z"
    - latency: 2.605624ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 2.351348ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 2.134463ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 2.463732ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 2.488761ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:36:59Z"
    - latency: 2.190425ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:35:59Z"
    - latency: 2.300866ms
      message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:22:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-117-to-network-check-target-ip-10-0-138-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-117.ec2.internal
      uid: 36109df9-04b0-426a-9dbe-e917f63ab9da
    resourceVersion: "21354"
    uid: 4559632d-4d5d-4728-b663-1e228b1cb49e
  spec:
    sourcePod: network-check-source-7cbc45fddc-pcsdm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:29:59Z"
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.950901ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:43:59Z"
    - latency: 2.205201ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:42:59Z"
    - latency: 2.350263ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:41:59Z"
    - latency: 2.610044ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 2.406536ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 2.196322ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 2.467231ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 2.163537ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:36:59Z"
    - latency: 2.270682ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:35:59Z"
    - latency: 2.03472ms
      message: 'network-check-target-ip-10-0-138-38: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:22:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-117-to-network-check-target-ip-10-0-140-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-117.ec2.internal
      uid: 36109df9-04b0-426a-9dbe-e917f63ab9da
    resourceVersion: "21352"
    uid: cc99283e-c979-44dc-9242-243e6adbda08
  spec:
    sourcePod: network-check-source-7cbc45fddc-pcsdm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:29:59Z"
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.315307ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:43:59Z"
    - latency: 929.72µs
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:42:59Z"
    - latency: 932.873µs
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:41:59Z"
    - latency: 1.095675ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 1.058429ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 947.922µs
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 1.33445ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 1.223523ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:36:59Z"
    - latency: 1.000125ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:35:59Z"
    - latency: 1.030121ms
      message: 'network-check-target-ip-10-0-140-117: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:34:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:22:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-117-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-117.ec2.internal
      uid: 36109df9-04b0-426a-9dbe-e917f63ab9da
    resourceVersion: "20396"
    uid: 35a47afd-fa43-4521-9857-e5325d63c02b
  spec:
    sourcePod: network-check-source-7cbc45fddc-pcsdm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:28:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 2.012232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:40:59Z"
    - latency: 1.312231ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 1.928534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:39:59Z"
    - latency: 956.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 2.075911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:38:59Z"
    - latency: 827.548µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 1.868328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:37:59Z"
    - latency: 844.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:36:59Z"
    - latency: 2.20698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:36:59Z"
kind: List
metadata:
  resourceVersion: ""