apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:50:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: bfcbcd64-5aaf-4696-92ea-4fd146cb0b92
    resourceVersion: "51303"
    uid: 7e7a11c0-4a43-44e1-8148-988586fe53fc
  spec:
    sourcePod: network-check-source-dbd9cf844-gcqcb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:57:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.362µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 1.059438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 1.176661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 1.111818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:22:56Z"
    - latency: 1.334743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:21:56Z"
    - latency: 968.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:20:56Z"
    - latency: 929.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:19:56Z"
    - latency: 1.021501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:18:56Z"
    - latency: 1.282752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:17:56Z"
    - latency: 928.393µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:50:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: bfcbcd64-5aaf-4696-92ea-4fd146cb0b92
    resourceVersion: "52269"
    uid: 7945e298-e8fa-4c13-ac7e-5bf815780e8a
  spec:
    sourcePod: network-check-source-dbd9cf844-gcqcb
    targetEndpoint: a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:56:56Z"
      message: 'load-balancer-api-external: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.608966ms
      message: 'load-balancer-api-external: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:26:56Z"
    - latency: 8.437137ms
      message: 'load-balancer-api-external: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:26:56Z"
    - latency: 4.969594ms
      message: 'load-balancer-api-external: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 8.327989ms
      message: 'load-balancer-api-external: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 4.567668ms
      message: 'load-balancer-api-external: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 6.560548ms
      message: 'load-balancer-api-external: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 4.106303ms
      message: 'load-balancer-api-external: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 8.171589ms
      message: 'load-balancer-api-external: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 4.637197ms
      message: 'load-balancer-api-external: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:22:56Z"
    - latency: 9.634394ms
      message: 'load-balancer-api-external: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:22:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:50:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: bfcbcd64-5aaf-4696-92ea-4fd146cb0b92
    resourceVersion: "52268"
    uid: 8bd6065d-91e7-4846-9832-3125e5215073
  spec:
    sourcePod: network-check-source-dbd9cf844-gcqcb
    targetEndpoint: a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:56:56Z"
      message: 'load-balancer-api-internal: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.569105ms
      message: 'load-balancer-api-internal: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:26:56Z"
    - latency: 8.340174ms
      message: 'load-balancer-api-internal: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:26:56Z"
    - latency: 4.976276ms
      message: 'load-balancer-api-internal: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 8.235719ms
      message: 'load-balancer-api-internal: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 4.57638ms
      message: 'load-balancer-api-internal: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 6.510963ms
      message: 'load-balancer-api-internal: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 4.554ms
      message: 'load-balancer-api-internal: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 8.181339ms
      message: 'load-balancer-api-internal: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 4.624525ms
      message: 'load-balancer-api-internal: tcp connection to a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:22:56Z"
    - latency: 9.691914ms
      message: 'load-balancer-api-internal: resolved host name a482ac908b3d846f19823596211ea9a7-b942cae591479fd0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:22:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:50:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-ip-10-0-128-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: bfcbcd64-5aaf-4696-92ea-4fd146cb0b92
    resourceVersion: "51300"
    uid: dcc50cca-41b8-4867-aa21-0a7c0cd56036
  spec:
    sourcePod: network-check-source-dbd9cf844-gcqcb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:57:56Z"
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 867.676µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 858.739µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 860.332µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 1.019696ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:22:56Z"
    - latency: 907.595µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:21:56Z"
    - latency: 911.8µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:20:56Z"
    - latency: 941.023µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:19:56Z"
    - latency: 1.377969ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:18:56Z"
    - latency: 1.001051ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:17:56Z"
    - latency: 876.451µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:50:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-ip-10-0-129-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: bfcbcd64-5aaf-4696-92ea-4fd146cb0b92
    resourceVersion: "51301"
    uid: 2a1e4957-dcce-4fe6-a78d-c33bb8c98f46
  spec:
    sourcePod: network-check-source-dbd9cf844-gcqcb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:57:56Z"
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.1983ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 2.275551ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 2.318598ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 2.197828ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:22:56Z"
    - latency: 2.142148ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:21:56Z"
    - latency: 2.318337ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:20:56Z"
    - latency: 2.01951ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:19:56Z"
    - latency: 2.060194ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:18:56Z"
    - latency: 2.209788ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:17:56Z"
    - latency: 2.200853ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:50:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-ip-10-0-143-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: bfcbcd64-5aaf-4696-92ea-4fd146cb0b92
    resourceVersion: "51302"
    uid: 958b1dc9-1163-4799-9fa4-d8b513112580
  spec:
    sourcePod: network-check-source-dbd9cf844-gcqcb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:57:56Z"
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.323117ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 2.71673ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 2.394719ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 2.101341ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:22:56Z"
    - latency: 2.63036ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:21:56Z"
    - latency: 2.519498ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:20:56Z"
    - latency: 2.296469ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:19:56Z"
    - latency: 2.390812ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:18:56Z"
    - latency: 2.29879ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:17:56Z"
    - latency: 2.242639ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T16:50:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: bfcbcd64-5aaf-4696-92ea-4fd146cb0b92
    resourceVersion: "52267"
    uid: b4bec4d1-2adf-4618-b026-67fa3586ad26
  spec:
    sourcePod: network-check-source-dbd9cf844-gcqcb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T16:56:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.741µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:26:56Z"
    - latency: 2.132779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:26:56Z"
    - latency: 885.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 1.811712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:25:56Z"
    - latency: 897.562µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 1.913274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:24:56Z"
    - latency: 929.447µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 1.736143ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:23:56Z"
    - latency: 1.013719ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:22:56Z"
    - latency: 1.680067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:22:56Z"
kind: List
metadata:
  resourceVersion: ""