apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-202-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-202.ec2.internal
      uid: 0047c851-86ac-48d6-9a9e-d12915bb8e70
    resourceVersion: "53610"
    uid: c4732fe8-5d43-44fe-88f2-fad4b4b18830
  spec:
    sourcePod: network-check-source-989f8b8dc-ljm5c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:49:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.68µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 980.681µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 1.422528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 829.221µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:49Z"
    - latency: 878.505µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:13:49Z"
    - latency: 839.092µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:12:49Z"
    - latency: 1.202598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:49Z"
    - latency: 1.715404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:49Z"
    - latency: 837.131µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:49Z"
    - latency: 1.139892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-202-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-202.ec2.internal
      uid: 0047c851-86ac-48d6-9a9e-d12915bb8e70
    resourceVersion: "54532"
    uid: 386832d6-8285-4d5a-a61a-0070688b3f7c
  spec:
    sourcePod: network-check-source-989f8b8dc-ljm5c
    targetEndpoint: ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:48:49Z"
      message: 'load-balancer-api-external: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.632945ms
      message: 'load-balancer-api-external: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:18:49Z"
    - latency: 7.695273ms
      message: 'load-balancer-api-external: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:18:49Z"
    - latency: 3.579837ms
      message: 'load-balancer-api-external: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 9.318992ms
      message: 'load-balancer-api-external: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 4.637687ms
      message: 'load-balancer-api-external: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 20.560498ms
      message: 'load-balancer-api-external: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 4.233441ms
      message: 'load-balancer-api-external: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 8.817758ms
      message: 'load-balancer-api-external: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 4.507339ms
      message: 'load-balancer-api-external: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:49Z"
    - latency: 7.282498ms
      message: 'load-balancer-api-external: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:14:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-202-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-202.ec2.internal
      uid: 0047c851-86ac-48d6-9a9e-d12915bb8e70
    resourceVersion: "54531"
    uid: 412c2d71-dd2f-4470-90e6-9a1899e21ced
  spec:
    sourcePod: network-check-source-989f8b8dc-ljm5c
    targetEndpoint: ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:48:49Z"
      message: 'load-balancer-api-internal: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.550845ms
      message: 'load-balancer-api-internal: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:18:49Z"
    - latency: 7.759804ms
      message: 'load-balancer-api-internal: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:18:49Z"
    - latency: 4.460831ms
      message: 'load-balancer-api-internal: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 9.436539ms
      message: 'load-balancer-api-internal: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 6.394108ms
      message: 'load-balancer-api-internal: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 20.625323ms
      message: 'load-balancer-api-internal: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 4.888943ms
      message: 'load-balancer-api-internal: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 8.754105ms
      message: 'load-balancer-api-internal: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 4.853127ms
      message: 'load-balancer-api-internal: tcp connection to ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:49Z"
    - latency: 7.344287ms
      message: 'load-balancer-api-internal: resolved host name ae4944c9a8ebb42d7aadecbbd95865b2-f748582617b25930.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:14:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-202-to-network-check-target-ip-10-0-134-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-202.ec2.internal
      uid: 0047c851-86ac-48d6-9a9e-d12915bb8e70
    resourceVersion: "53607"
    uid: 81727a5c-2fec-4cf9-b6bd-947a1b25c56a
  spec:
    sourcePod: network-check-source-989f8b8dc-ljm5c
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:49:49Z"
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.315172ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 1.032559ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 1.734299ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 880.365µs
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:49Z"
    - latency: 1.189051ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:13:49Z"
    - latency: 1.641897ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:12:49Z"
    - latency: 1.416309ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:49Z"
    - latency: 895.389µs
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:49Z"
    - latency: 923.518µs
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:49Z"
    - latency: 851.882µs
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-202-to-network-check-target-ip-10-0-134-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-202.ec2.internal
      uid: 0047c851-86ac-48d6-9a9e-d12915bb8e70
    resourceVersion: "53608"
    uid: eea4bab2-7c39-46df-a686-3fd3e12bddbb
  spec:
    sourcePod: network-check-source-989f8b8dc-ljm5c
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:49:49Z"
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.293305ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 1.938889ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 2.588098ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 2.148475ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:49Z"
    - latency: 2.192226ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:13:49Z"
    - latency: 2.240092ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:12:49Z"
    - latency: 2.533823ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:49Z"
    - latency: 2.245436ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:49Z"
    - latency: 2.349451ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:49Z"
    - latency: 2.093032ms
      message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-202-to-network-check-target-ip-10-0-138-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-202.ec2.internal
      uid: 0047c851-86ac-48d6-9a9e-d12915bb8e70
    resourceVersion: "53609"
    uid: 96aa0715-9670-484f-907e-cd35e7064186
  spec:
    sourcePod: network-check-source-989f8b8dc-ljm5c
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:49:49Z"
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.08351ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 1.985225ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 1.911022ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 2.044381ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:49Z"
    - latency: 1.653921ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:13:49Z"
    - latency: 1.947695ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:12:49Z"
    - latency: 1.961245ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:11:49Z"
    - latency: 1.998105ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:10:49Z"
    - latency: 1.771633ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:09:49Z"
    - latency: 1.866771ms
      message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-202-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-202.ec2.internal
      uid: 0047c851-86ac-48d6-9a9e-d12915bb8e70
    resourceVersion: "54529"
    uid: 02ce8b2a-5ed9-4b42-a123-93b26a83fa67
  spec:
    sourcePod: network-check-source-989f8b8dc-ljm5c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:48:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.464µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:18:49Z"
    - latency: 1.813121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:18:49Z"
    - latency: 984.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 2.147162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:17:49Z"
    - latency: 1.035747ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 1.697706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:16:49Z"
    - latency: 983.109µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 1.6863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:15:49Z"
    - latency: 1.156682ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:49Z"
    - latency: 1.690311ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:14:49Z"
kind: List
metadata:
  resourceVersion: ""