apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:19:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 371f7234-b857-4ae2-a1f5-28f2f4fe4173
    resourceVersion: "65222"
    uid: 735f16be-92d3-40a9-9e1b-f1b5173bbb59
  spec:
    sourcePod: network-check-source-7d88cb55d8-wxhgh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:26:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.212208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 988.896µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 938.795µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 1.24137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 952.437µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:57:28Z"
    - latency: 1.041672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:56:28Z"
    - latency: 1.082834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:55:28Z"
    - latency: 1.188897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:54:28Z"
    - latency: 946.622µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:53:28Z"
    - latency: 966.903µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:19:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 371f7234-b857-4ae2-a1f5-28f2f4fe4173
    resourceVersion: "65223"
    uid: 3ba783cd-3423-42d1-bff9-fe503c561177
  spec:
    sourcePod: network-check-source-7d88cb55d8-wxhgh
    targetEndpoint: acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:25:28Z"
      message: 'load-balancer-api-external: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.846605ms
      message: 'load-balancer-api-external: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 8.189242ms
      message: 'load-balancer-api-external: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 3.172656ms
      message: 'load-balancer-api-external: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 11.050907ms
      message: 'load-balancer-api-external: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 4.03801ms
      message: 'load-balancer-api-external: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 9.051111ms
      message: 'load-balancer-api-external: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 3.818206ms
      message: 'load-balancer-api-external: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 8.02113ms
      message: 'load-balancer-api-external: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 4.834838ms
      message: 'load-balancer-api-external: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:57:28Z"
    - latency: 8.441651ms
      message: 'load-balancer-api-external: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:57:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:19:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 371f7234-b857-4ae2-a1f5-28f2f4fe4173
    resourceVersion: "65224"
    uid: 3bb992e6-59c1-47b1-91b7-53a9c508bf28
  spec:
    sourcePod: network-check-source-7d88cb55d8-wxhgh
    targetEndpoint: acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:25:28Z"
      message: 'load-balancer-api-internal: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.149101ms
      message: 'load-balancer-api-internal: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 8.316883ms
      message: 'load-balancer-api-internal: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 3.17615ms
      message: 'load-balancer-api-internal: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 11.185177ms
      message: 'load-balancer-api-internal: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 5.846295ms
      message: 'load-balancer-api-internal: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 9.231488ms
      message: 'load-balancer-api-internal: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 5.81678ms
      message: 'load-balancer-api-internal: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 8.068901ms
      message: 'load-balancer-api-internal: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 4.831653ms
      message: 'load-balancer-api-internal: tcp connection to acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:57:28Z"
    - latency: 8.55855ms
      message: 'load-balancer-api-internal: resolved host name acdea94de4997472583998ef46d50eb0-85916ff9a3a48ff6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:57:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:19:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-ip-10-0-132-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 371f7234-b857-4ae2-a1f5-28f2f4fe4173
    resourceVersion: "65218"
    uid: f109807b-294e-4104-99d9-bb6a44cd49ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-wxhgh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:26:28Z"
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 849.905µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 1.182701ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 1.094042ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 1.511798ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 1.120008ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:57:28Z"
    - latency: 865.468µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:56:28Z"
    - latency: 859.268µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:55:28Z"
    - latency: 1.209406ms
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:54:28Z"
    - latency: 901.255µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:53:28Z"
    - latency: 865.292µs
      message: 'network-check-target-ip-10-0-132-132: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:19:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-ip-10-0-139-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 371f7234-b857-4ae2-a1f5-28f2f4fe4173
    resourceVersion: "65220"
    uid: 67ac5c49-1e5a-4583-b49a-c9e471b7b607
  spec:
    sourcePod: network-check-source-7d88cb55d8-wxhgh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:26:28Z"
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.442831ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 2.10263ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 2.378353ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 2.304821ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 2.441716ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:57:28Z"
    - latency: 2.345457ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:56:28Z"
    - latency: 2.843117ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:55:28Z"
    - latency: 2.787146ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:54:28Z"
    - latency: 2.567454ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:53:28Z"
    - latency: 2.422675ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:19:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-ip-10-0-143-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 371f7234-b857-4ae2-a1f5-28f2f4fe4173
    resourceVersion: "65219"
    uid: 2fc81323-38bf-4e54-ac5e-011b4d22f54a
  spec:
    sourcePod: network-check-source-7d88cb55d8-wxhgh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:26:28Z"
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.393101ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 2.793202ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 2.381704ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 2.438768ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 2.242195ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:57:28Z"
    - latency: 2.43521ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:56:28Z"
    - latency: 2.238965ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:55:28Z"
    - latency: 2.018548ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:54:28Z"
    - latency: 1.890444ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:53:28Z"
    - latency: 2.21644ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T22:19:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-132.ec2.internal
      uid: 371f7234-b857-4ae2-a1f5-28f2f4fe4173
    resourceVersion: "65221"
    uid: b67d0d77-cac2-4737-af75-fd149c9faf7f
  spec:
    sourcePod: network-check-source-7d88cb55d8-wxhgh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T22:25:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 873.964µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 1.859503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:01:28Z"
    - latency: 1.259227ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 1.800676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T23:00:28Z"
    - latency: 757.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 1.57675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:59:28Z"
    - latency: 1.247633ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 1.532838ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:58:28Z"
    - latency: 1.058703ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T22:57:28Z"
    - latency: 1.634303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T22:57:28Z"
kind: List
metadata:
  resourceVersion: ""