apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 302a4790-5486-46e3-a992-f5f076fdfa07
    resourceVersion: "36899"
    uid: d2ad48a1-35ad-4e62-a3d1-b1f4bdc64d28
  spec:
    sourcePod: network-check-source-869dcfcdcd-gnzzs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.039005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:11:59Z"
    - latency: 1.085565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:10:59Z"
    - latency: 889.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:59Z"
    - latency: 836.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 884.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 1.402741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 1.395843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 912.243µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:59Z"
    - latency: 759.835µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:59Z"
    - latency: 878.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 302a4790-5486-46e3-a992-f5f076fdfa07
    resourceVersion: "34660"
    uid: 31995a47-4ade-45b7-80d6-87f4de4bc1e6
  spec:
    sourcePod: network-check-source-869dcfcdcd-gnzzs
    targetEndpoint: a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:59Z"
      message: 'load-balancer-api-external: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.313639ms
      message: 'load-balancer-api-external: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 7.690544ms
      message: 'load-balancer-api-external: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 4.417245ms
      message: 'load-balancer-api-external: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 9.422787ms
      message: 'load-balancer-api-external: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 6.004974ms
      message: 'load-balancer-api-external: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 10.217018ms
      message: 'load-balancer-api-external: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 5.441408ms
      message: 'load-balancer-api-external: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 9.086099ms
      message: 'load-balancer-api-external: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 4.302336ms
      message: 'load-balancer-api-external: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:59Z"
    - latency: 9.317209ms
      message: 'load-balancer-api-external: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 302a4790-5486-46e3-a992-f5f076fdfa07
    resourceVersion: "34661"
    uid: c3d5b245-daf7-4e44-8b52-41b00df51152
  spec:
    sourcePod: network-check-source-869dcfcdcd-gnzzs
    targetEndpoint: a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:59Z"
      message: 'load-balancer-api-internal: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.343027ms
      message: 'load-balancer-api-internal: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 7.663367ms
      message: 'load-balancer-api-internal: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 4.45952ms
      message: 'load-balancer-api-internal: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 9.349951ms
      message: 'load-balancer-api-internal: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 6.061277ms
      message: 'load-balancer-api-internal: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 10.146761ms
      message: 'load-balancer-api-internal: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 5.415418ms
      message: 'load-balancer-api-internal: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 9.013212ms
      message: 'load-balancer-api-internal: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 4.18814ms
      message: 'load-balancer-api-internal: tcp connection to a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:59Z"
    - latency: 9.290307ms
      message: 'load-balancer-api-internal: resolved host name a028f193f3709420dab1b0f366d22cde-1be51a06738c0f06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-128-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 302a4790-5486-46e3-a992-f5f076fdfa07
    resourceVersion: "36897"
    uid: ff727a17-543c-45fb-bdba-703aefae6151
  spec:
    sourcePod: network-check-source-869dcfcdcd-gnzzs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:59Z"
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.870112ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:11:59Z"
    - latency: 1.778064ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:10:59Z"
    - latency: 2.182027ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:59Z"
    - latency: 1.876349ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 1.690534ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 2.158175ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 2.150441ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 2.119474ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:59Z"
    - latency: 1.869776ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:59Z"
    - latency: 2.075244ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-131-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 302a4790-5486-46e3-a992-f5f076fdfa07
    resourceVersion: "36896"
    uid: 07966515-9414-4ae3-a7f0-3994a412c950
  spec:
    sourcePod: network-check-source-869dcfcdcd-gnzzs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:59Z"
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.401641ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:11:59Z"
    - latency: 949.666µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:10:59Z"
    - latency: 800.651µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:59Z"
    - latency: 1.129574ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 770.544µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 1.02097ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 1.073721ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 1.241741ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:59Z"
    - latency: 1.071822ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:59Z"
    - latency: 1.357353ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-140-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 302a4790-5486-46e3-a992-f5f076fdfa07
    resourceVersion: "36898"
    uid: a7f8a5db-9bd2-437d-83b2-3462116e6aa5
  spec:
    sourcePod: network-check-source-869dcfcdcd-gnzzs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:59Z"
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.413847ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:11:59Z"
    - latency: 2.046923ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:10:59Z"
    - latency: 1.792685ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:59Z"
    - latency: 1.925416ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 2.140579ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 2.654853ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 2.392927ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 2.295678ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:59Z"
    - latency: 2.024963ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:59Z"
    - latency: 2.443033ms
      message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: 302a4790-5486-46e3-a992-f5f076fdfa07
    resourceVersion: "34658"
    uid: 7a4922dd-9dde-4569-9fb0-5e04f1971e68
  spec:
    sourcePod: network-check-source-869dcfcdcd-gnzzs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.641µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 2.00201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:08:59Z"
    - latency: 854.856µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 2.244768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:07:59Z"
    - latency: 850.587µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 2.024173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:06:59Z"
    - latency: 1.014339ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 2.384389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:59Z"
    - latency: 1.120244ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:59Z"
    - latency: 2.174043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:59Z"
kind: List
metadata:
  resourceVersion: ""