apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-63.ec2.internal
      uid: e3bd4c64-6a29-408e-80d6-32a3a51d1756
    resourceVersion: "32579"
    uid: 770f5265-c15a-461c-bb39-f80c9dd21e3d
  spec:
    sourcePod: network-check-source-685456655f-7f8gm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 998.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 921.199µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 1.060867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 995.897µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 1.016379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:00:33Z"
    - latency: 1.155041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:59:33Z"
    - latency: 1.100975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:58:33Z"
    - latency: 981.065µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:57:33Z"
    - latency: 1.06848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:56:33Z"
    - latency: 1.066728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:55:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-63.ec2.internal
      uid: e3bd4c64-6a29-408e-80d6-32a3a51d1756
    resourceVersion: "32581"
    uid: e6656f8a-9097-4a87-b2a8-a2f735878220
  spec:
    sourcePod: network-check-source-685456655f-7f8gm
    targetEndpoint: ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:36Z"
      message: 'load-balancer-api-external: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.968828ms
      message: 'load-balancer-api-external: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 6.692164ms
      message: 'load-balancer-api-external: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 4.45897ms
      message: 'load-balancer-api-external: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 6.722818ms
      message: 'load-balancer-api-external: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 4.884155ms
      message: 'load-balancer-api-external: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 6.475103ms
      message: 'load-balancer-api-external: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 4.735593ms
      message: 'load-balancer-api-external: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 6.667048ms
      message: 'load-balancer-api-external: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 4.64529ms
      message: 'load-balancer-api-external: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:00:33Z"
    - latency: 6.780252ms
      message: 'load-balancer-api-external: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:00:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-63.ec2.internal
      uid: e3bd4c64-6a29-408e-80d6-32a3a51d1756
    resourceVersion: "32580"
    uid: 4e09ac44-eb5b-4337-b23f-2aae46a224e6
  spec:
    sourcePod: network-check-source-685456655f-7f8gm
    targetEndpoint: ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:33Z"
      message: 'load-balancer-api-internal: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.071556ms
      message: 'load-balancer-api-internal: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 6.599444ms
      message: 'load-balancer-api-internal: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 4.494243ms
      message: 'load-balancer-api-internal: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 6.624411ms
      message: 'load-balancer-api-internal: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 4.69236ms
      message: 'load-balancer-api-internal: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 6.52708ms
      message: 'load-balancer-api-internal: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 4.775399ms
      message: 'load-balancer-api-internal: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 6.631702ms
      message: 'load-balancer-api-internal: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 4.666931ms
      message: 'load-balancer-api-internal: tcp connection to ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:00:33Z"
    - latency: 6.703078ms
      message: 'load-balancer-api-internal: resolved host name ac37a1e8218d5484cbec97f3a3e7d453-93ca6af6cbb6238d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:00:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-63-to-network-check-target-ip-10-0-128-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-63.ec2.internal
      uid: e3bd4c64-6a29-408e-80d6-32a3a51d1756
    resourceVersion: "32575"
    uid: ea629022-2551-46b7-86f0-1128f73c4218
  spec:
    sourcePod: network-check-source-685456655f-7f8gm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:33Z"
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.348µs
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 1.236546ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 992.982µs
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 1.441353ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 1.336618ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:00:33Z"
    - latency: 1.113729ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:59:33Z"
    - latency: 972.909µs
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:58:33Z"
    - latency: 1.011317ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:57:33Z"
    - latency: 866.78µs
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:56:33Z"
    - latency: 947.862µs
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:55:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-63-to-network-check-target-ip-10-0-130-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-63.ec2.internal
      uid: e3bd4c64-6a29-408e-80d6-32a3a51d1756
    resourceVersion: "32576"
    uid: bf50839a-04bd-48a9-b07b-0e540078f4cb
  spec:
    sourcePod: network-check-source-685456655f-7f8gm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:33Z"
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.459937ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 2.268479ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 2.321577ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 3.718378ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 2.16046ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:00:33Z"
    - latency: 1.965424ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:59:33Z"
    - latency: 2.268834ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:58:33Z"
    - latency: 1.955474ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:57:33Z"
    - latency: 2.385265ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:56:33Z"
    - latency: 2.268596ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:55:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-63-to-network-check-target-ip-10-0-138-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-63.ec2.internal
      uid: e3bd4c64-6a29-408e-80d6-32a3a51d1756
    resourceVersion: "32578"
    uid: 74bf1a6d-3506-4aa3-b611-d9f01e076aa3
  spec:
    sourcePod: network-check-source-685456655f-7f8gm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:29:33Z"
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.97116ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 2.781673ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 2.421513ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 2.443808ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 2.720354ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:00:33Z"
    - latency: 2.352161ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:59:33Z"
    - latency: 2.51345ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:58:33Z"
    - latency: 2.559765ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:57:33Z"
    - latency: 2.519932ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:56:33Z"
    - latency: 2.279092ms
      message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:55:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:22:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-63.ec2.internal
      uid: e3bd4c64-6a29-408e-80d6-32a3a51d1756
    resourceVersion: "32577"
    uid: f26044d5-1e76-45d8-83c0-bdd2571d25dc
  spec:
    sourcePod: network-check-source-685456655f-7f8gm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.126353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 2.205901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:04:33Z"
    - latency: 1.164341ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 1.619622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:03:33Z"
    - latency: 889.419µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 1.708523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:02:33Z"
    - latency: 777.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 1.755562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:01:33Z"
    - latency: 902.686µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T03:00:33Z"
    - latency: 1.841005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T03:00:33Z"
kind: List
metadata:
  resourceVersion: ""