apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:46:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-3-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-3.ec2.internal
      uid: 1ddb5e61-db3e-437d-a9a0-f41bfec5725e
    resourceVersion: "20960"
    uid: d87f7802-ef00-4e96-a63d-977d58b31d22
  spec:
    sourcePod: network-check-source-6947749cfc-2gj8s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:53:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007467ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 984.119µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:06:16Z"
    - latency: 741.748µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:05:16Z"
    - latency: 887.295µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:04:16Z"
    - latency: 899.822µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:03:16Z"
    - latency: 952.097µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:02:16Z"
    - latency: 787.804µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:01:16Z"
    - latency: 833.544µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:00:16Z"
    - latency: 1.065632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:59:16Z"
    - latency: 1.117831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:58:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:46:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-3-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-3.ec2.internal
      uid: 1ddb5e61-db3e-437d-a9a0-f41bfec5725e
    resourceVersion: "22476"
    uid: 8b49a3fd-b951-4c9f-96e0-cd4137bc21d9
  spec:
    sourcePod: network-check-source-6947749cfc-2gj8s
    targetEndpoint: a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:52:16Z"
      message: 'load-balancer-api-external: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.038725ms
      message: 'load-balancer-api-external: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:10:16Z"
    - latency: 8.619498ms
      message: 'load-balancer-api-external: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:10:16Z"
    - latency: 4.072724ms
      message: 'load-balancer-api-external: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:09:16Z"
    - latency: 10.318391ms
      message: 'load-balancer-api-external: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:09:16Z"
    - latency: 4.61994ms
      message: 'load-balancer-api-external: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:08:16Z"
    - latency: 9.193831ms
      message: 'load-balancer-api-external: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:08:16Z"
    - latency: 4.563212ms
      message: 'load-balancer-api-external: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 8.837433ms
      message: 'load-balancer-api-external: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 4.127868ms
      message: 'load-balancer-api-external: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:06:16Z"
    - latency: 10.181844ms
      message: 'load-balancer-api-external: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:06:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:46:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-3-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-3.ec2.internal
      uid: 1ddb5e61-db3e-437d-a9a0-f41bfec5725e
    resourceVersion: "22477"
    uid: e6f3a4bb-cab6-4745-a1cc-5056cf278eed
  spec:
    sourcePod: network-check-source-6947749cfc-2gj8s
    targetEndpoint: a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:52:16Z"
      message: 'load-balancer-api-internal: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.062341ms
      message: 'load-balancer-api-internal: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:10:16Z"
    - latency: 8.542309ms
      message: 'load-balancer-api-internal: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:10:16Z"
    - latency: 4.987318ms
      message: 'load-balancer-api-internal: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:09:16Z"
    - latency: 10.392754ms
      message: 'load-balancer-api-internal: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:09:16Z"
    - latency: 4.613414ms
      message: 'load-balancer-api-internal: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:08:16Z"
    - latency: 9.099225ms
      message: 'load-balancer-api-internal: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:08:16Z"
    - latency: 4.530665ms
      message: 'load-balancer-api-internal: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 8.886492ms
      message: 'load-balancer-api-internal: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 4.08996ms
      message: 'load-balancer-api-internal: tcp connection to a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:06:16Z"
    - latency: 10.105074ms
      message: 'load-balancer-api-internal: resolved host name a7487f7f61e374ab2b7a3674c647578f-814747e812250b76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:06:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:46:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-3-to-network-check-target-ip-10-0-134-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-3.ec2.internal
      uid: 1ddb5e61-db3e-437d-a9a0-f41bfec5725e
    resourceVersion: "20957"
    uid: 49dbe99c-32a4-449c-8550-0120a89256aa
  spec:
    sourcePod: network-check-source-6947749cfc-2gj8s
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:53:16Z"
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.295189ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 1.273979ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:06:16Z"
    - latency: 718.487µs
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:05:16Z"
    - latency: 786.583µs
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:04:16Z"
    - latency: 906.085µs
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:03:16Z"
    - latency: 949.253µs
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:02:16Z"
    - latency: 782.493µs
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:01:16Z"
    - latency: 1.502309ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:00:16Z"
    - latency: 1.017798ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:59:16Z"
    - latency: 1.067675ms
      message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:58:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:46:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-3-to-network-check-target-ip-10-0-135-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-3.ec2.internal
      uid: 1ddb5e61-db3e-437d-a9a0-f41bfec5725e
    resourceVersion: "20959"
    uid: 08aedb29-8d4c-4bd6-a666-3767dc510155
  spec:
    sourcePod: network-check-source-6947749cfc-2gj8s
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:53:16Z"
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.173178ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 2.057002ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:06:16Z"
    - latency: 1.96417ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:05:16Z"
    - latency: 2.532471ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:04:16Z"
    - latency: 2.152233ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:03:16Z"
    - latency: 2.109014ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:02:16Z"
    - latency: 2.057725ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:01:16Z"
    - latency: 2.164651ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:00:16Z"
    - latency: 2.513402ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:59:16Z"
    - latency: 2.058301ms
      message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:58:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:46:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-3-to-network-check-target-ip-10-0-138-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-3.ec2.internal
      uid: 1ddb5e61-db3e-437d-a9a0-f41bfec5725e
    resourceVersion: "20958"
    uid: dc9d3d96-4177-433b-8b66-98beb606eb5b
  spec:
    sourcePod: network-check-source-6947749cfc-2gj8s
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:53:16Z"
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.761735ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 2.112409ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:06:16Z"
    - latency: 1.769936ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:05:16Z"
    - latency: 1.861406ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:04:16Z"
    - latency: 2.031002ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:03:16Z"
    - latency: 2.011662ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:02:16Z"
    - latency: 1.942429ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:01:16Z"
    - latency: 1.932683ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:00:16Z"
    - latency: 2.005244ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:59:16Z"
    - latency: 1.855875ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T23:58:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T23:46:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-3-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-3.ec2.internal
      uid: 1ddb5e61-db3e-437d-a9a0-f41bfec5725e
    resourceVersion: "22475"
    uid: b9f2431f-da22-4035-87e4-8d7408282adc
  spec:
    sourcePod: network-check-source-6947749cfc-2gj8s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T23:52:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.107202ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:10:16Z"
    - latency: 1.744045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:10:16Z"
    - latency: 1.05648ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:09:16Z"
    - latency: 1.803206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:09:16Z"
    - latency: 1.002223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:08:16Z"
    - latency: 2.006851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:08:16Z"
    - latency: 1.077172ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 2.023949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:07:16Z"
    - latency: 840.912µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T00:06:16Z"
    - latency: 2.259617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T00:06:16Z"
kind: List
metadata:
  resourceVersion: ""