apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:17:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-202-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-202.ec2.internal
      uid: 39edf820-585e-43f2-966b-c902a50fa078
    resourceVersion: "45261"
    uid: 49d47c6c-fba3-4f4f-9214-6116c8bcd270
  spec:
    sourcePod: network-check-source-6947749cfc-7ckd7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:24:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.176564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 1.143878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 805.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:43:39Z"
    - latency: 1.129324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:42:39Z"
    - latency: 830.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:41:39Z"
    - latency: 854.39µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:40:39Z"
    - latency: 1.06759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:39:39Z"
    - latency: 1.138716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:38:39Z"
    - latency: 1.261459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:37:39Z"
    - latency: 965.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:36:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:17:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-202-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-202.ec2.internal
      uid: 39edf820-585e-43f2-966b-c902a50fa078
    resourceVersion: "46958"
    uid: e2a3cb46-d320-4621-8acd-aa9b3e6a23e6
  spec:
    sourcePod: network-check-source-6947749cfc-7ckd7
    targetEndpoint: aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:23:39Z"
      message: 'load-balancer-api-external: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.476704ms
      message: 'load-balancer-api-external: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:47:39Z"
    - latency: 7.885605ms
      message: 'load-balancer-api-external: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:47:39Z"
    - latency: 4.075909ms
      message: 'load-balancer-api-external: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:46:39Z"
    - latency: 8.566705ms
      message: 'load-balancer-api-external: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:46:39Z"
    - latency: 4.993668ms
      message: 'load-balancer-api-external: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 7.695959ms
      message: 'load-balancer-api-external: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 5.692786ms
      message: 'load-balancer-api-external: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 10.070996ms
      message: 'load-balancer-api-external: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 4.589576ms
      message: 'load-balancer-api-external: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:43:39Z"
    - latency: 7.831669ms
      message: 'load-balancer-api-external: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:43:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:17:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-202-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-202.ec2.internal
      uid: 39edf820-585e-43f2-966b-c902a50fa078
    resourceVersion: "46959"
    uid: a2cee018-ab9a-4d80-8fca-4a9fb9db04c1
  spec:
    sourcePod: network-check-source-6947749cfc-7ckd7
    targetEndpoint: aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:23:39Z"
      message: 'load-balancer-api-internal: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.475266ms
      message: 'load-balancer-api-internal: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:47:39Z"
    - latency: 7.980731ms
      message: 'load-balancer-api-internal: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:47:39Z"
    - latency: 4.091891ms
      message: 'load-balancer-api-internal: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:46:39Z"
    - latency: 8.616829ms
      message: 'load-balancer-api-internal: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:46:39Z"
    - latency: 4.83626ms
      message: 'load-balancer-api-internal: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 7.750403ms
      message: 'load-balancer-api-internal: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 5.684862ms
      message: 'load-balancer-api-internal: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 10.116931ms
      message: 'load-balancer-api-internal: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 4.554676ms
      message: 'load-balancer-api-internal: tcp connection to aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:43:39Z"
    - latency: 7.882252ms
      message: 'load-balancer-api-internal: resolved host name aada2c1a1c5a547f382d160b673aabac-da5b3aa201719a15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:43:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:17:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-202-to-network-check-target-ip-10-0-131-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-202.ec2.internal
      uid: 39edf820-585e-43f2-966b-c902a50fa078
    resourceVersion: "45257"
    uid: aee16a91-e3b3-40d9-ae10-79ce681228a5
  spec:
    sourcePod: network-check-source-6947749cfc-7ckd7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:24:39Z"
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.422µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 841.093µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 987.784µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:43:39Z"
    - latency: 1.470135ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:42:39Z"
    - latency: 919.353µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:41:39Z"
    - latency: 922.23µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:40:39Z"
    - latency: 801.45µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:39:39Z"
    - latency: 821.879µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:38:39Z"
    - latency: 960.845µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:37:39Z"
    - latency: 976.698µs
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:36:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:17:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-202-to-network-check-target-ip-10-0-135-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-202.ec2.internal
      uid: 39edf820-585e-43f2-966b-c902a50fa078
    resourceVersion: "45260"
    uid: 654efd5e-7e49-4dbe-b749-459e8d49cc3e
  spec:
    sourcePod: network-check-source-6947749cfc-7ckd7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:24:39Z"
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212694ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 2.155539ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 2.433039ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:43:39Z"
    - latency: 1.859307ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:42:39Z"
    - latency: 1.934944ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:41:39Z"
    - latency: 1.960139ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:40:39Z"
    - latency: 2.892942ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:39:39Z"
    - latency: 2.10186ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:38:39Z"
    - latency: 2.159222ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:37:39Z"
    - latency: 2.224314ms
      message: 'network-check-target-ip-10-0-135-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:36:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:17:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-202-to-network-check-target-ip-10-0-140-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-202.ec2.internal
      uid: 39edf820-585e-43f2-966b-c902a50fa078
    resourceVersion: "45258"
    uid: d70cc3c5-9787-4f69-9f93-3f97154785fe
  spec:
    sourcePod: network-check-source-6947749cfc-7ckd7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:24:39Z"
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.925178ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 1.932901ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 1.789491ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:43:39Z"
    - latency: 1.907089ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:42:39Z"
    - latency: 1.675675ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:41:39Z"
    - latency: 1.641353ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:40:39Z"
    - latency: 1.689589ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:39:39Z"
    - latency: 1.99559ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:38:39Z"
    - latency: 1.659126ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:37:39Z"
    - latency: 1.706084ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:36:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:17:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-202-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-202.ec2.internal
      uid: 39edf820-585e-43f2-966b-c902a50fa078
    resourceVersion: "46956"
    uid: cd6d0bdd-1627-4b9a-80f2-4e63500f725d
  spec:
    sourcePod: network-check-source-6947749cfc-7ckd7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:23:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.557µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:47:39Z"
    - latency: 2.091901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:47:39Z"
    - latency: 1.245251ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:46:39Z"
    - latency: 1.763695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:46:39Z"
    - latency: 970.214µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 1.718368ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:45:39Z"
    - latency: 904.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 1.73299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:44:39Z"
    - latency: 1.131943ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:43:39Z"
    - latency: 1.62453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:43:39Z"
kind: List
metadata:
  resourceVersion: ""