apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:02:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 49e226d1-60d7-40ae-893f-b3ac6fab5256
    resourceVersion: "67920"
    uid: 631de9db-677e-4101-9da6-2b5037de97a3
  spec:
    sourcePod: network-check-source-6f8b768455-wx768
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:09:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.121318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 796.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 1.278742ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 1.257817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:34:56Z"
    - latency: 1.237494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:33:56Z"
    - latency: 1.536608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:32:56Z"
    - latency: 1.296409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:31:56Z"
    - latency: 2.333601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:30:56Z"
    - latency: 863.627µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:56Z"
    - latency: 1.314847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:02:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 49e226d1-60d7-40ae-893f-b3ac6fab5256
    resourceVersion: "68808"
    uid: 7fc76874-0698-4cbd-9fc7-1261dc297ffd
  spec:
    sourcePod: network-check-source-6f8b768455-wx768
    targetEndpoint: ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:08:56Z"
      message: 'load-balancer-api-external: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.519593ms
      message: 'load-balancer-api-external: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:38:56Z"
    - latency: 8.150427ms
      message: 'load-balancer-api-external: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:38:56Z"
    - latency: 6.09291ms
      message: 'load-balancer-api-external: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 7.267247ms
      message: 'load-balancer-api-external: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 4.447884ms
      message: 'load-balancer-api-external: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 8.831152ms
      message: 'load-balancer-api-external: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 4.2899ms
      message: 'load-balancer-api-external: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 10.136349ms
      message: 'load-balancer-api-external: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 4.435473ms
      message: 'load-balancer-api-external: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:34:56Z"
    - latency: 7.091624ms
      message: 'load-balancer-api-external: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:34:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:02:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 49e226d1-60d7-40ae-893f-b3ac6fab5256
    resourceVersion: "68809"
    uid: 9e5068dd-d242-4874-95bb-cda33f7f67b7
  spec:
    sourcePod: network-check-source-6f8b768455-wx768
    targetEndpoint: ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:08:56Z"
      message: 'load-balancer-api-internal: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.285295ms
      message: 'load-balancer-api-internal: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:38:56Z"
    - latency: 8.099365ms
      message: 'load-balancer-api-internal: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:38:56Z"
    - latency: 5.026918ms
      message: 'load-balancer-api-internal: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 7.185247ms
      message: 'load-balancer-api-internal: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 4.664704ms
      message: 'load-balancer-api-internal: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 8.772996ms
      message: 'load-balancer-api-internal: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 4.318674ms
      message: 'load-balancer-api-internal: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 10.040683ms
      message: 'load-balancer-api-internal: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 4.374361ms
      message: 'load-balancer-api-internal: tcp connection to ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:34:56Z"
    - latency: 7.132818ms
      message: 'load-balancer-api-internal: resolved host name ae8ba6ebc71e74497ad81952461a7d1a-6252ff89190c2390.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:34:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:02:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-129-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 49e226d1-60d7-40ae-893f-b3ac6fab5256
    resourceVersion: "67919"
    uid: 3f1c45c5-8d70-415a-b802-8bd820e20d87
  spec:
    sourcePod: network-check-source-6f8b768455-wx768
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:09:56Z"
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.418196ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 2.296848ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 2.138766ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 1.977918ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:34:56Z"
    - latency: 2.31607ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:33:56Z"
    - latency: 2.498662ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:32:56Z"
    - latency: 2.174089ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:31:56Z"
    - latency: 2.05827ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:30:56Z"
    - latency: 3.472546ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:56Z"
    - latency: 2.44659ms
      message: 'network-check-target-ip-10-0-129-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:02:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-135-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 49e226d1-60d7-40ae-893f-b3ac6fab5256
    resourceVersion: "67918"
    uid: 4c07a558-b379-475c-a7ab-428f79bffa5b
  spec:
    sourcePod: network-check-source-6f8b768455-wx768
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:09:56Z"
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.293472ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 1.857977ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 1.976314ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 2.090927ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:34:56Z"
    - latency: 2.173378ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:33:56Z"
    - latency: 2.190661ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:32:56Z"
    - latency: 2.157703ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:31:56Z"
    - latency: 1.499562ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:30:56Z"
    - latency: 1.823342ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:56Z"
    - latency: 2.007712ms
      message: 'network-check-target-ip-10-0-135-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:02:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-136-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 49e226d1-60d7-40ae-893f-b3ac6fab5256
    resourceVersion: "67917"
    uid: d04c7849-a8a2-43dc-a31e-0e97541a8e71
  spec:
    sourcePod: network-check-source-6f8b768455-wx768
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:09:56Z"
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.419717ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 870.372µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 963.894µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 992.316µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:34:56Z"
    - latency: 1.081944ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:33:56Z"
    - latency: 1.904966ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:32:56Z"
    - latency: 1.50233ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:31:56Z"
    - latency: 1.333404ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:30:56Z"
    - latency: 943.974µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:56Z"
    - latency: 1.094451ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:02:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 49e226d1-60d7-40ae-893f-b3ac6fab5256
    resourceVersion: "68807"
    uid: 3daa547d-6e8f-45da-9c61-62d0be29f692
  spec:
    sourcePod: network-check-source-6f8b768455-wx768
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:08:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:38:56Z"
    - latency: 2.29152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:38:56Z"
    - latency: 947.397µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 1.614097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:37:56Z"
    - latency: 917.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 1.845705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:36:56Z"
    - latency: 997.593µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 1.649949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:35:56Z"
    - latency: 1.103192ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:34:56Z"
    - latency: 1.931125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:34:56Z"
kind: List
metadata:
  resourceVersion: ""