apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T22:33:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-66.ec2.internal
      uid: 8c19a87c-b752-45a4-820d-3108d1838f69
    resourceVersion: "39730"
    uid: fdbc737e-1e33-4767-bae9-57d2643a0d9e
  spec:
    sourcePod: network-check-source-8894fc9bd-lb8gp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T22:40:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:29:54Z"
    - latency: 1.060113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:28:54Z"
    - latency: 858.798µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 979.46µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 1.31167ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 1.37366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 982.283µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:23:54Z"
    - latency: 1.048117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:22:54Z"
    - latency: 908.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:21:54Z"
    - latency: 837.302µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T22:33:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-66.ec2.internal
      uid: 8c19a87c-b752-45a4-820d-3108d1838f69
    resourceVersion: "38789"
    uid: a2a00fae-5002-4f7a-b52b-b43e686896e2
  spec:
    sourcePod: network-check-source-8894fc9bd-lb8gp
    targetEndpoint: a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T22:39:54Z"
      message: 'load-balancer-api-external: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.893814ms
      message: 'load-balancer-api-external: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 8.579251ms
      message: 'load-balancer-api-external: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 5.284673ms
      message: 'load-balancer-api-external: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 9.269331ms
      message: 'load-balancer-api-external: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 4.974718ms
      message: 'load-balancer-api-external: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 8.170406ms
      message: 'load-balancer-api-external: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 4.816322ms
      message: 'load-balancer-api-external: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 9.243807ms
      message: 'load-balancer-api-external: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 5.068442ms
      message: 'load-balancer-api-external: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:23:54Z"
    - latency: 8.269414ms
      message: 'load-balancer-api-external: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:23:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T22:33:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-66.ec2.internal
      uid: 8c19a87c-b752-45a4-820d-3108d1838f69
    resourceVersion: "38788"
    uid: 2ef0b551-200d-4735-9d90-41071d1a5c46
  spec:
    sourcePod: network-check-source-8894fc9bd-lb8gp
    targetEndpoint: a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T22:39:54Z"
      message: 'load-balancer-api-internal: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.941978ms
      message: 'load-balancer-api-internal: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 8.473844ms
      message: 'load-balancer-api-internal: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 5.236917ms
      message: 'load-balancer-api-internal: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 9.390831ms
      message: 'load-balancer-api-internal: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 4.960687ms
      message: 'load-balancer-api-internal: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 8.112687ms
      message: 'load-balancer-api-internal: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 4.804785ms
      message: 'load-balancer-api-internal: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 9.217704ms
      message: 'load-balancer-api-internal: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 5.10611ms
      message: 'load-balancer-api-internal: tcp connection to a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:23:54Z"
    - latency: 8.191645ms
      message: 'load-balancer-api-internal: resolved host name a35693dfbc3ef44af8fd80d40047da29-ce2f1560b4f20c2b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:23:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T22:33:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-66-to-network-check-target-ip-10-0-134-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-66.ec2.internal
      uid: 8c19a87c-b752-45a4-820d-3108d1838f69
    resourceVersion: "39728"
    uid: 093ae7de-c421-4771-a9d5-2207193f10f7
  spec:
    sourcePod: network-check-source-8894fc9bd-lb8gp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T22:40:54Z"
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.956067ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:29:54Z"
    - latency: 2.129952ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:28:54Z"
    - latency: 2.256415ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 2.065751ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 2.270243ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 2.422253ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 2.153099ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:23:54Z"
    - latency: 2.140596ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:22:54Z"
    - latency: 2.163563ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:21:54Z"
    - latency: 1.957368ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T22:33:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-66-to-network-check-target-ip-10-0-136-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-66.ec2.internal
      uid: 8c19a87c-b752-45a4-820d-3108d1838f69
    resourceVersion: "39727"
    uid: e7e96a4e-24ff-4f6a-81b8-962dd5835c70
  spec:
    sourcePod: network-check-source-8894fc9bd-lb8gp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T22:40:54Z"
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.883µs
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:29:54Z"
    - latency: 890.152µs
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:28:54Z"
    - latency: 1.105636ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 830.734µs
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 1.085091ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 739.889µs
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 721.55µs
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:23:54Z"
    - latency: 1.191861ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:22:54Z"
    - latency: 875.579µs
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:21:54Z"
    - latency: 823.571µs
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T22:33:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-66-to-network-check-target-ip-10-0-142-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-66.ec2.internal
      uid: 8c19a87c-b752-45a4-820d-3108d1838f69
    resourceVersion: "39729"
    uid: b9295897-d35d-4782-be11-abdef3f38128
  spec:
    sourcePod: network-check-source-8894fc9bd-lb8gp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T22:40:54Z"
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.321532ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:29:54Z"
    - latency: 2.154167ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:28:54Z"
    - latency: 2.182208ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 2.519868ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 2.163939ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 2.397778ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 2.578402ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:23:54Z"
    - latency: 2.174541ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:22:54Z"
    - latency: 1.863761ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:21:54Z"
    - latency: 2.04343ms
      message: 'network-check-target-ip-10-0-142-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T22:33:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-66.ec2.internal
      uid: 8c19a87c-b752-45a4-820d-3108d1838f69
    resourceVersion: "38787"
    uid: 1b8e7e07-29b4-47b2-a428-12b56ad3e4a4
  spec:
    sourcePod: network-check-source-8894fc9bd-lb8gp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T22:39:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.240299ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 1.817416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:27:54Z"
    - latency: 1.243015ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 1.63017ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:26:54Z"
    - latency: 870.893µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 1.564983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:25:54Z"
    - latency: 807.017µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 2.035912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:24:54Z"
    - latency: 1.037947ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T23:23:54Z"
    - latency: 1.595975ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T23:23:54Z"
kind: List
metadata:
  resourceVersion: ""