apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:55:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-189.ec2.internal
      uid: f6c18213-d5d2-426e-a25a-b8a205445264
    resourceVersion: "22614"
    uid: b1935361-8d77-481e-848e-cfa3e0861290
  spec:
    sourcePod: network-check-source-6f8b768455-wwv7l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T08:02:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.234471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:23:01Z"
    - latency: 1.021707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:22:01Z"
    - latency: 1.203098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:21:01Z"
    - latency: 1.129534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:20:01Z"
    - latency: 954.753µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 1.300889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 977.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 1.375433ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 1.480194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:15:01Z"
    - latency: 783.574µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:55:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-189.ec2.internal
      uid: f6c18213-d5d2-426e-a25a-b8a205445264
    resourceVersion: "20727"
    uid: 191b1b6f-6d21-45a9-bce5-e6bbde7bf826
  spec:
    sourcePod: network-check-source-6f8b768455-wwv7l
    targetEndpoint: ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T08:01:01Z"
      message: 'load-balancer-api-external: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.622102ms
      message: 'load-balancer-api-external: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 8.913231ms
      message: 'load-balancer-api-external: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 3.988135ms
      message: 'load-balancer-api-external: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 11.952845ms
      message: 'load-balancer-api-external: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 3.79089ms
      message: 'load-balancer-api-external: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 12.604209ms
      message: 'load-balancer-api-external: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 4.913007ms
      message: 'load-balancer-api-external: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 11.631275ms
      message: 'load-balancer-api-external: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 4.874903ms
      message: 'load-balancer-api-external: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:15:01Z"
    - latency: 13.831217ms
      message: 'load-balancer-api-external: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:15:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:55:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-189.ec2.internal
      uid: f6c18213-d5d2-426e-a25a-b8a205445264
    resourceVersion: "20726"
    uid: 7c81830f-25ce-4db6-93c0-5d8a39fb51c6
  spec:
    sourcePod: network-check-source-6f8b768455-wwv7l
    targetEndpoint: ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T08:01:01Z"
      message: 'load-balancer-api-internal: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.240609ms
      message: 'load-balancer-api-internal: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 8.852061ms
      message: 'load-balancer-api-internal: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 3.950499ms
      message: 'load-balancer-api-internal: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 11.990581ms
      message: 'load-balancer-api-internal: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 4.509261ms
      message: 'load-balancer-api-internal: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 12.571493ms
      message: 'load-balancer-api-internal: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 4.930144ms
      message: 'load-balancer-api-internal: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 11.705507ms
      message: 'load-balancer-api-internal: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 4.836754ms
      message: 'load-balancer-api-internal: tcp connection to ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:15:01Z"
    - latency: 13.862167ms
      message: 'load-balancer-api-internal: resolved host name ac11a4678ccbf429983d919bd5bc5bc1-070beec493ed825c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:15:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:55:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-189-to-network-check-target-ip-10-0-132-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-189.ec2.internal
      uid: f6c18213-d5d2-426e-a25a-b8a205445264
    resourceVersion: "22612"
    uid: 730664f4-ed14-4526-b269-fa76c7e8eb73
  spec:
    sourcePod: network-check-source-6f8b768455-wwv7l
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T08:02:01Z"
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.173117ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:23:01Z"
    - latency: 2.22533ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:22:01Z"
    - latency: 2.040419ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:21:01Z"
    - latency: 2.252704ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:20:01Z"
    - latency: 2.258212ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 2.162265ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 1.647452ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 2.191273ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 1.874442ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:15:01Z"
    - latency: 2.052201ms
      message: 'network-check-target-ip-10-0-132-163: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:55:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-189-to-network-check-target-ip-10-0-134-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-189.ec2.internal
      uid: f6c18213-d5d2-426e-a25a-b8a205445264
    resourceVersion: "22611"
    uid: 06d69092-9c05-4cf3-b6ba-a02b73c06487
  spec:
    sourcePod: network-check-source-6f8b768455-wwv7l
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T08:02:01Z"
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.318165ms
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:23:01Z"
    - latency: 1.743095ms
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:22:01Z"
    - latency: 1.018019ms
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:21:01Z"
    - latency: 813.329µs
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:20:01Z"
    - latency: 957.022µs
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 815.346µs
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 952.476µs
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 1.14109ms
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 771.587µs
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:15:01Z"
    - latency: 1.339567ms
      message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:55:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-189-to-network-check-target-ip-10-0-137-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-189.ec2.internal
      uid: f6c18213-d5d2-426e-a25a-b8a205445264
    resourceVersion: "22613"
    uid: ba4dd785-c032-457d-94fc-5079bd86af48
  spec:
    sourcePod: network-check-source-6f8b768455-wwv7l
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T08:02:01Z"
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.877611ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:23:01Z"
    - latency: 2.192966ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:22:01Z"
    - latency: 1.700583ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:21:01Z"
    - latency: 1.812771ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:20:01Z"
    - latency: 1.996786ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 1.83206ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 1.673682ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 1.890557ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 1.596319ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:15:01Z"
    - latency: 2.010345ms
      message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T07:55:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-189.ec2.internal
      uid: f6c18213-d5d2-426e-a25a-b8a205445264
    resourceVersion: "20725"
    uid: 01fd6090-9bf3-41b7-9e45-0136c02e7d52
  spec:
    sourcePod: network-check-source-6f8b768455-wwv7l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T08:01:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.186µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 1.575061ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:19:01Z"
    - latency: 855.153µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 1.7752ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:18:01Z"
    - latency: 758.416µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 1.942222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:17:01Z"
    - latency: 1.091983ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 1.88219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:16:01Z"
    - latency: 827.924µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T08:15:01Z"
    - latency: 2.191303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T08:15:01Z"
kind: List
metadata:
  resourceVersion: ""