apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:08:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-158-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-158.ec2.internal
      uid: 8eff35a8-fc53-454f-ad96-6603847f1329
    resourceVersion: "39320"
    uid: 1cf4272d-111d-4121-ac60-1c509ff0e042
  spec:
    sourcePod: network-check-source-7cbc45fddc-p7895
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:15:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 790.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:38Z"
    - latency: 871.101µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 867.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 969.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 1.63631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 1.05231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:52:38Z"
    - latency: 1.00225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:51:38Z"
    - latency: 833.155µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:50:38Z"
    - latency: 914.7µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:49:38Z"
    - latency: 974.965µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:08:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-158-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-158.ec2.internal
      uid: 8eff35a8-fc53-454f-ad96-6603847f1329
    resourceVersion: "38858"
    uid: e60e6444-5389-44f1-bcfb-dd9288f724d0
  spec:
    sourcePod: network-check-source-7cbc45fddc-p7895
    targetEndpoint: a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:14:38Z"
      message: 'load-balancer-api-external: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.854453ms
      message: 'load-balancer-api-external: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 7.832042ms
      message: 'load-balancer-api-external: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 6.713857ms
      message: 'load-balancer-api-external: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 7.964761ms
      message: 'load-balancer-api-external: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 5.358178ms
      message: 'load-balancer-api-external: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 7.903948ms
      message: 'load-balancer-api-external: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 5.197383ms
      message: 'load-balancer-api-external: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 6.683345ms
      message: 'load-balancer-api-external: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 6.001892ms
      message: 'load-balancer-api-external: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:52:38Z"
    - latency: 8.320467ms
      message: 'load-balancer-api-external: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:52:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:08:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-158-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-158.ec2.internal
      uid: 8eff35a8-fc53-454f-ad96-6603847f1329
    resourceVersion: "38857"
    uid: 387c6f63-13b6-49cb-bff5-555002ee12aa
  spec:
    sourcePod: network-check-source-7cbc45fddc-p7895
    targetEndpoint: a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:14:38Z"
      message: 'load-balancer-api-internal: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.907581ms
      message: 'load-balancer-api-internal: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 7.866877ms
      message: 'load-balancer-api-internal: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 6.725548ms
      message: 'load-balancer-api-internal: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 7.9392ms
      message: 'load-balancer-api-internal: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 5.275385ms
      message: 'load-balancer-api-internal: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 8.020258ms
      message: 'load-balancer-api-internal: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 5.263706ms
      message: 'load-balancer-api-internal: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 6.635717ms
      message: 'load-balancer-api-internal: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 6.005366ms
      message: 'load-balancer-api-internal: tcp connection to a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:52:38Z"
    - latency: 8.348292ms
      message: 'load-balancer-api-internal: resolved host name a0eeae1ed2e4248a79c165dff53c2127-4126bc5522837785.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:52:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:08:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-158-to-network-check-target-ip-10-0-133-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-158.ec2.internal
      uid: 8eff35a8-fc53-454f-ad96-6603847f1329
    resourceVersion: "39317"
    uid: 75c68512-94ee-43d2-bf10-6e22972279be
  spec:
    sourcePod: network-check-source-7cbc45fddc-p7895
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:15:38Z"
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.625µs
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:38Z"
    - latency: 1.574461ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 869.23µs
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 943.151µs
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 1.069888ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 919.073µs
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:52:38Z"
    - latency: 1.481159ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:51:38Z"
    - latency: 846.958µs
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:50:38Z"
    - latency: 873.8µs
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:49:38Z"
    - latency: 828.752µs
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:08:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-158-to-network-check-target-ip-10-0-134-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-158.ec2.internal
      uid: 8eff35a8-fc53-454f-ad96-6603847f1329
    resourceVersion: "39319"
    uid: 66019dd5-befb-4faa-abf0-59fe2437818d
  spec:
    sourcePod: network-check-source-7cbc45fddc-p7895
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:15:38Z"
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.893814ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:38Z"
    - latency: 2.50193ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 2.175569ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 2.346309ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 2.472535ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 2.280627ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:52:38Z"
    - latency: 2.016233ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:51:38Z"
    - latency: 2.196659ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:50:38Z"
    - latency: 2.046588ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:49:38Z"
    - latency: 2.193003ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:08:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-158-to-network-check-target-ip-10-0-140-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-158.ec2.internal
      uid: 8eff35a8-fc53-454f-ad96-6603847f1329
    resourceVersion: "39318"
    uid: b466c5b9-038f-4898-8586-1663b919491b
  spec:
    sourcePod: network-check-source-7cbc45fddc-p7895
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:15:38Z"
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.91476ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:57:38Z"
    - latency: 2.068464ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 1.689277ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 1.987801ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 1.914344ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 1.915782ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:52:38Z"
    - latency: 1.932013ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:51:38Z"
    - latency: 2.181441ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:50:38Z"
    - latency: 1.774999ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:49:38Z"
    - latency: 1.906308ms
      message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T19:08:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-158-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-158.ec2.internal
      uid: 8eff35a8-fc53-454f-ad96-6603847f1329
    resourceVersion: "38856"
    uid: 699a1f07-6c0c-4335-97ed-84f7bfae8371
  spec:
    sourcePod: network-check-source-7cbc45fddc-p7895
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T19:14:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.305981ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 2.052945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:56:38Z"
    - latency: 878.226µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 1.689235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:55:38Z"
    - latency: 925.528µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 1.560661ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:54:38Z"
    - latency: 848.115µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 1.897038ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:53:38Z"
    - latency: 943.593µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:52:38Z"
    - latency: 1.785422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:52:38Z"
kind: List
metadata:
  resourceVersion: ""