apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T12:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-55.ec2.internal
      uid: a9cc009a-7327-4753-828c-b84b6c948a20
    resourceVersion: "44840"
    uid: 8bbbd93d-5aba-4624-8780-b5ad2f11768a
  spec:
    sourcePod: network-check-source-8894fc9bd-6gh7r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T12:43:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.222072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 979.045µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 1.044713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:02:39Z"
    - latency: 968.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:01:39Z"
    - latency: 1.378513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:00:39Z"
    - latency: 1.148824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:59:39Z"
    - latency: 1.18221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:58:39Z"
    - latency: 853.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:57:39Z"
    - latency: 837.191µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:56:39Z"
    - latency: 1.124611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T12:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-55.ec2.internal
      uid: a9cc009a-7327-4753-828c-b84b6c948a20
    resourceVersion: "46774"
    uid: 5be0fd60-5e7d-433d-aaed-edc82d076391
  spec:
    sourcePod: network-check-source-8894fc9bd-6gh7r
    targetEndpoint: a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T12:42:39Z"
      message: 'load-balancer-api-external: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.477804ms
      message: 'load-balancer-api-external: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:06:39Z"
    - latency: 8.415928ms
      message: 'load-balancer-api-external: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:06:39Z"
    - latency: 3.074743ms
      message: 'load-balancer-api-external: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:05:39Z"
    - latency: 8.475965ms
      message: 'load-balancer-api-external: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:05:39Z"
    - latency: 2.502187ms
      message: 'load-balancer-api-external: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 8.3345ms
      message: 'load-balancer-api-external: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 5.204662ms
      message: 'load-balancer-api-external: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 7.847044ms
      message: 'load-balancer-api-external: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 3.885432ms
      message: 'load-balancer-api-external: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:02:39Z"
    - latency: 8.27922ms
      message: 'load-balancer-api-external: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T12:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-55.ec2.internal
      uid: a9cc009a-7327-4753-828c-b84b6c948a20
    resourceVersion: "46775"
    uid: 6d63dbe6-8e57-4fc4-8bd9-ac34a489a518
  spec:
    sourcePod: network-check-source-8894fc9bd-6gh7r
    targetEndpoint: a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T12:42:39Z"
      message: 'load-balancer-api-internal: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.493192ms
      message: 'load-balancer-api-internal: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:06:39Z"
    - latency: 8.287946ms
      message: 'load-balancer-api-internal: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:06:39Z"
    - latency: 4.54619ms
      message: 'load-balancer-api-internal: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:05:39Z"
    - latency: 8.410458ms
      message: 'load-balancer-api-internal: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:05:39Z"
    - latency: 5.678551ms
      message: 'load-balancer-api-internal: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 8.406696ms
      message: 'load-balancer-api-internal: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 4.578312ms
      message: 'load-balancer-api-internal: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 7.868866ms
      message: 'load-balancer-api-internal: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 4.578627ms
      message: 'load-balancer-api-internal: tcp connection to a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:02:39Z"
    - latency: 8.316604ms
      message: 'load-balancer-api-internal: resolved host name a3b47ce2e0fa140d386c0785cc6abb7e-052e62a4fbebe909.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T12:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-55-to-network-check-target-ip-10-0-129-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-55.ec2.internal
      uid: a9cc009a-7327-4753-828c-b84b6c948a20
    resourceVersion: "44838"
    uid: 382a09df-21c8-41df-9753-26f3d7a3b87d
  spec:
    sourcePod: network-check-source-8894fc9bd-6gh7r
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T12:43:39Z"
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.945724ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 2.439628ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 1.965192ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:02:39Z"
    - latency: 2.150919ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:01:39Z"
    - latency: 2.086896ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:00:39Z"
    - latency: 2.460971ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:59:39Z"
    - latency: 2.159242ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:58:39Z"
    - latency: 1.968483ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:57:39Z"
    - latency: 1.887574ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:56:39Z"
    - latency: 1.85681ms
      message: 'network-check-target-ip-10-0-129-233: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T12:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-55-to-network-check-target-ip-10-0-140-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-55.ec2.internal
      uid: a9cc009a-7327-4753-828c-b84b6c948a20
    resourceVersion: "44839"
    uid: 3962e394-1290-45eb-85da-9000f4af507c
  spec:
    sourcePod: network-check-source-8894fc9bd-6gh7r
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T12:43:39Z"
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.057162ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 1.742902ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 1.928197ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:02:39Z"
    - latency: 2.148537ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:01:39Z"
    - latency: 2.017011ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:00:39Z"
    - latency: 2.171034ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:59:39Z"
    - latency: 1.86221ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:58:39Z"
    - latency: 1.905219ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:57:39Z"
    - latency: 1.969387ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:56:39Z"
    - latency: 1.963114ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T12:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-55-to-network-check-target-ip-10-0-142-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-55.ec2.internal
      uid: a9cc009a-7327-4753-828c-b84b6c948a20
    resourceVersion: "44837"
    uid: 4f28d6df-bb22-4329-b26f-d2c3a62cd39d
  spec:
    sourcePod: network-check-source-8894fc9bd-6gh7r
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T12:43:39Z"
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.385µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 834.258µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 876.213µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:02:39Z"
    - latency: 875.74µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:01:39Z"
    - latency: 1.488397ms
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:00:39Z"
    - latency: 926.423µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:59:39Z"
    - latency: 860.823µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:58:39Z"
    - latency: 1.1163ms
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:57:39Z"
    - latency: 907.728µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:56:39Z"
    - latency: 930.376µs
      message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T12:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-19T12:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-55.ec2.internal
      uid: a9cc009a-7327-4753-828c-b84b6c948a20
    resourceVersion: "46773"
    uid: 26ee9d39-8a30-4f68-91d5-7ff8ae812814
  spec:
    sourcePod: network-check-source-8894fc9bd-6gh7r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-19T12:42:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.255µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:06:39Z"
    - latency: 1.93726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:06:39Z"
    - latency: 903.386µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:05:39Z"
    - latency: 1.708092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:05:39Z"
    - latency: 1.081076ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 1.739466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:04:39Z"
    - latency: 1.022867ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 1.635506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:03:39Z"
    - latency: 875.38µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-19T13:02:39Z"
    - latency: 1.771058ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-19T13:02:39Z"
kind: List
metadata:
  resourceVersion: ""