apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-15-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-15.ec2.internal
      uid: 0939b69d-69bb-4634-915b-6b41e075111b
    resourceVersion: "63603"
    uid: 9c79c4de-a89f-4283-a83c-eccdaad1f9e7
  spec:
    sourcePod: network-check-source-869dcfcdcd-76jl8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:09:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.298123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 1.072455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 1.229831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 844.298µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 822.232µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:40:25Z"
    - latency: 832.855µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:39:25Z"
    - latency: 1.081345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:38:25Z"
    - latency: 766.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:37:25Z"
    - latency: 962.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:36:25Z"
    - latency: 913.506µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-15-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-15.ec2.internal
      uid: 0939b69d-69bb-4634-915b-6b41e075111b
    resourceVersion: "63605"
    uid: adc08306-a747-4496-b472-ca4899043bb2
  spec:
    sourcePod: network-check-source-869dcfcdcd-76jl8
    targetEndpoint: a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:08:25Z"
      message: 'load-balancer-api-external: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.074673ms
      message: 'load-balancer-api-external: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 8.240283ms
      message: 'load-balancer-api-external: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 6.179666ms
      message: 'load-balancer-api-external: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 6.601413ms
      message: 'load-balancer-api-external: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 5.093458ms
      message: 'load-balancer-api-external: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 6.138243ms
      message: 'load-balancer-api-external: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 4.219418ms
      message: 'load-balancer-api-external: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 10.294901ms
      message: 'load-balancer-api-external: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 3.77488ms
      message: 'load-balancer-api-external: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:40:25Z"
    - latency: 6.874342ms
      message: 'load-balancer-api-external: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:40:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-15-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-15.ec2.internal
      uid: 0939b69d-69bb-4634-915b-6b41e075111b
    resourceVersion: "63604"
    uid: 06703059-f976-4925-aaf1-44c4089ed455
  spec:
    sourcePod: network-check-source-869dcfcdcd-76jl8
    targetEndpoint: a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:08:25Z"
      message: 'load-balancer-api-internal: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.972139ms
      message: 'load-balancer-api-internal: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 8.250162ms
      message: 'load-balancer-api-internal: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 6.246399ms
      message: 'load-balancer-api-internal: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 6.540561ms
      message: 'load-balancer-api-internal: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 3.903268ms
      message: 'load-balancer-api-internal: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 6.205074ms
      message: 'load-balancer-api-internal: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 4.184637ms
      message: 'load-balancer-api-internal: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 10.333999ms
      message: 'load-balancer-api-internal: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 3.805238ms
      message: 'load-balancer-api-internal: tcp connection to a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:40:25Z"
    - latency: 6.853536ms
      message: 'load-balancer-api-internal: resolved host name a50f3f7ae92754404a08b1fe80048724-e4d2b8c78769352f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:40:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-15-to-network-check-target-ip-10-0-130-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-15.ec2.internal
      uid: 0939b69d-69bb-4634-915b-6b41e075111b
    resourceVersion: "63600"
    uid: bb62caff-2029-4f68-9724-d77a994086a9
  spec:
    sourcePod: network-check-source-869dcfcdcd-76jl8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:09:25Z"
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.277806ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 2.446715ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 2.216564ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 1.93426ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 2.294937ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:40:25Z"
    - latency: 2.073124ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:39:25Z"
    - latency: 2.412436ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:38:25Z"
    - latency: 2.196325ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:37:25Z"
    - latency: 1.906161ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:36:25Z"
    - latency: 2.277794ms
      message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-15-to-network-check-target-ip-10-0-135-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-15.ec2.internal
      uid: 0939b69d-69bb-4634-915b-6b41e075111b
    resourceVersion: "63599"
    uid: 21e7bd9a-23d4-4563-aa1b-39243e2c4f18
  spec:
    sourcePod: network-check-source-869dcfcdcd-76jl8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:09:25Z"
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.309666ms
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 790.557µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 920.035µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 773.463µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 857.575µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:40:25Z"
    - latency: 873.883µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:39:25Z"
    - latency: 880.18µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:38:25Z"
    - latency: 829.558µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:37:25Z"
    - latency: 910.38µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:36:25Z"
    - latency: 905.402µs
      message: 'network-check-target-ip-10-0-135-15: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-15-to-network-check-target-ip-10-0-135-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-15.ec2.internal
      uid: 0939b69d-69bb-4634-915b-6b41e075111b
    resourceVersion: "63601"
    uid: d92d65c3-2c7c-4aba-a277-730f6a94c554
  spec:
    sourcePod: network-check-source-869dcfcdcd-76jl8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:09:25Z"
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.742913ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 2.430836ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 2.258899ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 2.395308ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 1.90567ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:40:25Z"
    - latency: 2.435299ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:39:25Z"
    - latency: 2.466781ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:38:25Z"
    - latency: 2.242158ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:37:25Z"
    - latency: 2.250615ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:36:25Z"
    - latency: 2.625706ms
      message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:35:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-15-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-15.ec2.internal
      uid: 0939b69d-69bb-4634-915b-6b41e075111b
    resourceVersion: "63602"
    uid: ab1cc451-3674-4fbc-8206-943520a68170
  spec:
    sourcePod: network-check-source-869dcfcdcd-76jl8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:08:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.134287ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 2.162591ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:44:25Z"
    - latency: 850.471µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 1.598889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:43:25Z"
    - latency: 981.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 1.800218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:42:25Z"
    - latency: 877.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 1.510086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:41:25Z"
    - latency: 1.161665ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:40:25Z"
    - latency: 1.598597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:40:25Z"
kind: List
metadata:
  resourceVersion: ""