apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-100-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-100.ec2.internal
      uid: 0d749a1d-5f70-451b-84ac-c473fea8acef
    resourceVersion: "53865"
    uid: 3644b3c9-f63f-4f76-bad8-b9e42d10ea03
  spec:
    sourcePod: network-check-source-6f8b768455-rc5g6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 1.187878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 974.937µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:25Z"
    - latency: 1.235628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:25Z"
    - latency: 1.227896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:25Z"
    - latency: 953.236µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:25Z"
    - latency: 976.02µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:25Z"
    - latency: 708.871µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:25Z"
    - latency: 1.235178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:25Z"
    - latency: 1.261565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-100-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-100.ec2.internal
      uid: 0d749a1d-5f70-451b-84ac-c473fea8acef
    resourceVersion: "55351"
    uid: 1a7a2f6e-a069-4c54-9484-da1bb2dacf84
  spec:
    sourcePod: network-check-source-6f8b768455-rc5g6
    targetEndpoint: aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:25Z"
      message: 'load-balancer-api-external: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.480728ms
      message: 'load-balancer-api-external: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:25Z"
    - latency: 10.121566ms
      message: 'load-balancer-api-external: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:25Z"
    - latency: 4.181774ms
      message: 'load-balancer-api-external: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:25Z"
    - latency: 7.702473ms
      message: 'load-balancer-api-external: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:25Z"
    - latency: 5.041487ms
      message: 'load-balancer-api-external: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 8.912314ms
      message: 'load-balancer-api-external: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 6.19127ms
      message: 'load-balancer-api-external: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 8.318117ms
      message: 'load-balancer-api-external: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 4.340491ms
      message: 'load-balancer-api-external: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:25Z"
    - latency: 7.859518ms
      message: 'load-balancer-api-external: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-100-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-100.ec2.internal
      uid: 0d749a1d-5f70-451b-84ac-c473fea8acef
    resourceVersion: "55352"
    uid: de7ab6b8-e4bd-4fda-a5db-5c49156118a4
  spec:
    sourcePod: network-check-source-6f8b768455-rc5g6
    targetEndpoint: aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:25Z"
      message: 'load-balancer-api-internal: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.763743ms
      message: 'load-balancer-api-internal: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:25Z"
    - latency: 10.059479ms
      message: 'load-balancer-api-internal: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:25Z"
    - latency: 3.651529ms
      message: 'load-balancer-api-internal: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:25Z"
    - latency: 7.675624ms
      message: 'load-balancer-api-internal: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:25Z"
    - latency: 5.088016ms
      message: 'load-balancer-api-internal: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 8.87038ms
      message: 'load-balancer-api-internal: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 6.166878ms
      message: 'load-balancer-api-internal: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 8.26513ms
      message: 'load-balancer-api-internal: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 5.224216ms
      message: 'load-balancer-api-internal: tcp connection to aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:25Z"
    - latency: 7.842366ms
      message: 'load-balancer-api-internal: resolved host name aac3db14753964129840f95d4045a205-233310ca75ee96f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-100-to-network-check-target-ip-10-0-129-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-100.ec2.internal
      uid: 0d749a1d-5f70-451b-84ac-c473fea8acef
    resourceVersion: "53863"
    uid: 6f9e2e75-46d4-459a-92b2-6e482f647d4c
  spec:
    sourcePod: network-check-source-6f8b768455-rc5g6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:25Z"
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.661185ms
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 1.100018ms
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 932.337µs
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:25Z"
    - latency: 997.51µs
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:25Z"
    - latency: 1.153631ms
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:25Z"
    - latency: 1.448822ms
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:25Z"
    - latency: 1.49573ms
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:25Z"
    - latency: 827.633µs
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:25Z"
    - latency: 1.49562ms
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:25Z"
    - latency: 983.735µs
      message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-100-to-network-check-target-ip-10-0-132-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-100.ec2.internal
      uid: 0d749a1d-5f70-451b-84ac-c473fea8acef
    resourceVersion: "53864"
    uid: 73c42f01-6741-4717-a692-c8a8120ed9e7
  spec:
    sourcePod: network-check-source-6f8b768455-rc5g6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:25Z"
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.440619ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 2.314092ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 2.059845ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:25Z"
    - latency: 1.80719ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:25Z"
    - latency: 2.60362ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:25Z"
    - latency: 2.151643ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:25Z"
    - latency: 2.473276ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:25Z"
    - latency: 1.724708ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:25Z"
    - latency: 2.382674ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:25Z"
    - latency: 2.221832ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-100-to-network-check-target-ip-10-0-138-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-100.ec2.internal
      uid: 0d749a1d-5f70-451b-84ac-c473fea8acef
    resourceVersion: "53862"
    uid: ad332b34-a112-4838-81bc-9b7cbfe2c457
  spec:
    sourcePod: network-check-source-6f8b768455-rc5g6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:25Z"
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.098012ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 2.28566ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 1.968789ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:25Z"
    - latency: 2.420128ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:25Z"
    - latency: 2.590175ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:25Z"
    - latency: 2.267173ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:25Z"
    - latency: 2.103632ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:25Z"
    - latency: 1.682995ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:25Z"
    - latency: 2.287651ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:25Z"
    - latency: 2.505604ms
      message: 'network-check-target-ip-10-0-138-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:01:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-100-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-100.ec2.internal
      uid: 0d749a1d-5f70-451b-84ac-c473fea8acef
    resourceVersion: "55349"
    uid: cbfbfaa8-c1d3-4bfb-afdc-72becfabb8d5
  spec:
    sourcePod: network-check-source-6f8b768455-rc5g6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.716µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:25Z"
    - latency: 1.850432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:25Z"
    - latency: 827.195µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:25Z"
    - latency: 1.752427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:25Z"
    - latency: 979.031µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 2.091953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:25Z"
    - latency: 813.298µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 1.885942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:25Z"
    - latency: 867.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:25Z"
    - latency: 2.282183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:25Z"
kind: List
metadata:
  resourceVersion: ""