apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-174-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-174.ec2.internal
      uid: bd9f3af5-dabc-4e7e-87bb-7fe806134c04
    resourceVersion: "52330"
    uid: d80c3ce8-a3f0-4242-a36e-7f3c23658bd2
  spec:
    sourcePod: network-check-source-dbd9cf844-mkjv6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:39:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.308µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:49Z"
    - latency: 1.206029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:49Z"
    - latency: 982.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:49Z"
    - latency: 1.551596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:49Z"
    - latency: 981.44µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:49Z"
    - latency: 975.243µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 1.20353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 1.010719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 1.097082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 1.317367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-174-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-174.ec2.internal
      uid: bd9f3af5-dabc-4e7e-87bb-7fe806134c04
    resourceVersion: "46831"
    uid: 76f09c99-6de2-4afa-bd49-e4b71c668cad
  spec:
    sourcePod: network-check-source-dbd9cf844-mkjv6
    targetEndpoint: abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:38:49Z"
      message: 'load-balancer-api-external: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.234197ms
      message: 'load-balancer-api-external: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 8.778085ms
      message: 'load-balancer-api-external: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 5.028166ms
      message: 'load-balancer-api-external: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 7.352751ms
      message: 'load-balancer-api-external: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 5.416937ms
      message: 'load-balancer-api-external: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 8.172332ms
      message: 'load-balancer-api-external: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 5.328881ms
      message: 'load-balancer-api-external: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 10.926024ms
      message: 'load-balancer-api-external: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 5.28793ms
      message: 'load-balancer-api-external: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:58:49Z"
    - latency: 6.755222ms
      message: 'load-balancer-api-external: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T19:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-174-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-174.ec2.internal
      uid: bd9f3af5-dabc-4e7e-87bb-7fe806134c04
    resourceVersion: "46830"
    uid: 5cf8eb54-9bb6-4e7e-be7e-ae72f3355df1
  spec:
    sourcePod: network-check-source-dbd9cf844-mkjv6
    targetEndpoint: abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:38:49Z"
      message: 'load-balancer-api-internal: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.164975ms
      message: 'load-balancer-api-internal: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 8.683346ms
      message: 'load-balancer-api-internal: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 5.035317ms
      message: 'load-balancer-api-internal: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 7.366954ms
      message: 'load-balancer-api-internal: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 5.386631ms
      message: 'load-balancer-api-internal: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 8.209774ms
      message: 'load-balancer-api-internal: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 5.277002ms
      message: 'load-balancer-api-internal: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 10.954848ms
      message: 'load-balancer-api-internal: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 4.011891ms
      message: 'load-balancer-api-internal: tcp connection to abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:58:49Z"
    - latency: 6.650152ms
      message: 'load-balancer-api-internal: resolved host name abcd81ce6285e431794a3ee3cd93fa03-43e9f0313b45c450.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T19:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-174-to-network-check-target-ip-10-0-136-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-174.ec2.internal
      uid: bd9f3af5-dabc-4e7e-87bb-7fe806134c04
    resourceVersion: "52327"
    uid: 6fec43a9-273c-479b-a35a-fe9f4116f4f6
  spec:
    sourcePod: network-check-source-dbd9cf844-mkjv6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:39:49Z"
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 843.316µs
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:49Z"
    - latency: 1.019521ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:49Z"
    - latency: 941.874µs
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:49Z"
    - latency: 1.527043ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:49Z"
    - latency: 871.636µs
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:49Z"
    - latency: 1.203297ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 1.02521ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 1.67319ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 991.8µs
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 1.365086ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-174-to-network-check-target-ip-10-0-137-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-174.ec2.internal
      uid: bd9f3af5-dabc-4e7e-87bb-7fe806134c04
    resourceVersion: "52328"
    uid: 3bf509ea-e56a-4ef0-9eba-9225c10f9fff
  spec:
    sourcePod: network-check-source-dbd9cf844-mkjv6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:39:49Z"
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.667076ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:49Z"
    - latency: 2.378405ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:49Z"
    - latency: 2.46787ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:49Z"
    - latency: 2.237458ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:49Z"
    - latency: 2.136915ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:49Z"
    - latency: 2.357189ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 2.277696ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 2.834919ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 2.337463ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 2.256606ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-174-to-network-check-target-ip-10-0-140-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-174.ec2.internal
      uid: bd9f3af5-dabc-4e7e-87bb-7fe806134c04
    resourceVersion: "52329"
    uid: fea20cc9-8255-4b50-bebc-ec4f7bacb4aa
  spec:
    sourcePod: network-check-source-dbd9cf844-mkjv6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:39:49Z"
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.297634ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:49Z"
    - latency: 2.357484ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:49Z"
    - latency: 2.465434ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:49Z"
    - latency: 2.617061ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:49Z"
    - latency: 2.718987ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:49Z"
    - latency: 2.48734ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 2.585071ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 2.61433ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 2.407446ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 2.573207ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-174-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-174.ec2.internal
      uid: bd9f3af5-dabc-4e7e-87bb-7fe806134c04
    resourceVersion: "46828"
    uid: e87f5a0d-b37b-48a3-bedc-eb718e3028ff
  spec:
    sourcePod: network-check-source-dbd9cf844-mkjv6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:38:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 830.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 2.058454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:02:49Z"
    - latency: 982.2µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 1.733959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:01:49Z"
    - latency: 1.180619ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 1.786547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:00:49Z"
    - latency: 1.526677ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 1.804955ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T19:59:49Z"
    - latency: 1.120625ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T19:58:49Z"
    - latency: 2.097011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T19:58:49Z"
kind: List
metadata:
  resourceVersion: ""