apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:24:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: 158ae4f1-d796-4fb5-bca7-fb1542b24d74
    resourceVersion: "162395"
    uid: 2f142f23-1e34-495c-9390-6dafbe2def82
  spec:
    sourcePod: network-check-source-6f78d59f99-sj6h8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:31:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.566789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 903.932µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:30Z"
    - latency: 1.797772ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:30Z"
    - latency: 1.468238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:30Z"
    - latency: 1.372524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:30Z"
    - latency: 1.615366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:22:30Z"
    - latency: 1.000731ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:21:30Z"
    - latency: 19.798303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:20:30Z"
    - latency: 1.057353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:19:30Z"
    - latency: 13.753092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:24:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: 158ae4f1-d796-4fb5-bca7-fb1542b24d74
    resourceVersion: "169204"
    uid: 756381cd-0ff4-4c78-9ff4-bdfae009921c
  spec:
    sourcePod: network-check-source-6f78d59f99-sj6h8
    targetEndpoint: ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:30:31Z"
      message: 'load-balancer-api-external: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.864151ms
      message: 'load-balancer-api-external: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:30Z"
    - latency: 17.967118ms
      message: 'load-balancer-api-external: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:30:30Z"
    - latency: 18.289506ms
      message: 'load-balancer-api-external: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:29:30Z"
    - latency: 7.294268ms
      message: 'load-balancer-api-external: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:29:30Z"
    - latency: 16.760052ms
      message: 'load-balancer-api-external: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:28:30Z"
    - latency: 7.589892ms
      message: 'load-balancer-api-external: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:28:30Z"
    - latency: 16.982534ms
      message: 'load-balancer-api-external: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 7.371198ms
      message: 'load-balancer-api-external: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 15.890741ms
      message: 'load-balancer-api-external: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:30Z"
    - latency: 6.66491ms
      message: 'load-balancer-api-external: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:26:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:24:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: 158ae4f1-d796-4fb5-bca7-fb1542b24d74
    resourceVersion: "169205"
    uid: b6db5f4b-a317-4e4c-a17c-1826e3f5246f
  spec:
    sourcePod: network-check-source-6f78d59f99-sj6h8
    targetEndpoint: ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:30:30Z"
      message: 'load-balancer-api-internal: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.751854ms
      message: 'load-balancer-api-internal: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:30Z"
    - latency: 18.260858ms
      message: 'load-balancer-api-internal: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:30:30Z"
    - latency: 18.720926ms
      message: 'load-balancer-api-internal: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:29:30Z"
    - latency: 7.329518ms
      message: 'load-balancer-api-internal: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:29:30Z"
    - latency: 27.406843ms
      message: 'load-balancer-api-internal: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:28:30Z"
    - latency: 7.611568ms
      message: 'load-balancer-api-internal: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:28:30Z"
    - latency: 17.715336ms
      message: 'load-balancer-api-internal: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 7.411266ms
      message: 'load-balancer-api-internal: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 15.218757ms
      message: 'load-balancer-api-internal: tcp connection to ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:30Z"
    - latency: 6.701947ms
      message: 'load-balancer-api-internal: resolved host name ab9861767f579421fac6d92bbed33b3a-e800827ccdfea283.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:26:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:24:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-ip-10-0-131-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: 158ae4f1-d796-4fb5-bca7-fb1542b24d74
    resourceVersion: "162390"
    uid: aa9a8a0a-d452-4fca-b15c-4cb34ee82d4f
  spec:
    sourcePod: network-check-source-6f78d59f99-sj6h8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:31:30Z"
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.101µs
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 1.05132ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:30Z"
    - latency: 1.188916ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:30Z"
    - latency: 1.067935ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:30Z"
    - latency: 1.279017ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:30Z"
    - latency: 1.101731ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:22:30Z"
    - latency: 842.765µs
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:21:30Z"
    - latency: 18.623906ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:20:30Z"
    - latency: 1.853508ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:19:30Z"
    - latency: 11.094713ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:24:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-ip-10-0-132-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: 158ae4f1-d796-4fb5-bca7-fb1542b24d74
    resourceVersion: "162391"
    uid: fe3ca8e3-a2ac-4d29-a74a-eb7c0dd4bf19
  spec:
    sourcePod: network-check-source-6f78d59f99-sj6h8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:31:30Z"
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.168435ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 2.305096ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:30Z"
    - latency: 2.661755ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:30Z"
    - latency: 2.822221ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:30Z"
    - latency: 2.652216ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:30Z"
    - latency: 2.750184ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:22:30Z"
    - latency: 2.640587ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:21:30Z"
    - latency: 27.635515ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:20:30Z"
    - latency: 14.665684ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:19:30Z"
    - latency: 13.739423ms
      message: 'network-check-target-ip-10-0-132-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:24:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-ip-10-0-136-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: 158ae4f1-d796-4fb5-bca7-fb1542b24d74
    resourceVersion: "162394"
    uid: 084fa940-fee6-4969-9279-3ebfad68e92b
  spec:
    sourcePod: network-check-source-6f78d59f99-sj6h8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:31:30Z"
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.026507ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 2.244464ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:30Z"
    - latency: 2.079762ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:25:30Z"
    - latency: 2.626158ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:24:30Z"
    - latency: 2.663141ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:23:30Z"
    - latency: 2.111561ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:22:30Z"
    - latency: 2.283895ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:21:30Z"
    - latency: 18.927254ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:20:30Z"
    - latency: 2.487022ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:19:30Z"
    - latency: 32.857775ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T16:24:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: 158ae4f1-d796-4fb5-bca7-fb1542b24d74
    resourceVersion: "169203"
    uid: 51b3fa8f-0ec7-48aa-9306-6e9069b9000f
  spec:
    sourcePod: network-check-source-6f78d59f99-sj6h8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T16:30:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.100714ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:30:30Z"
    - latency: 7.946774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:30:30Z"
    - latency: 1.256681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:29:30Z"
    - latency: 1.796519ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:29:30Z"
    - latency: 1.199197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:28:30Z"
    - latency: 2.113825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:28:30Z"
    - latency: 1.180119ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 1.910399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:27:30Z"
    - latency: 1.507139ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T17:26:30Z"
    - latency: 1.874284ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T17:26:30Z"
kind: List
metadata:
  resourceVersion: ""