apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T19:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e5c5100b-93ff-4f1d-8a91-69a0205e747b
    resourceVersion: "43540"
    uid: ae4f4219-20d3-4958-873b-e26b70c82b36
  spec:
    sourcePod: network-check-source-7f44b6dd87-kxg9n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T19:41:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.644µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:02:52Z"
    - latency: 798.994µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:01:52Z"
    - latency: 1.01048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:00:52Z"
    - latency: 1.445239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:59:52Z"
    - latency: 1.411327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 897.523µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 1.325505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 976.694µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 1.180417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:54:52Z"
    - latency: 1.330498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T19:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e5c5100b-93ff-4f1d-8a91-69a0205e747b
    resourceVersion: "39405"
    uid: d2a3e259-f9c2-4fb4-8d1f-9b868835534f
  spec:
    sourcePod: network-check-source-7f44b6dd87-kxg9n
    targetEndpoint: a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T19:40:52Z"
      message: 'load-balancer-api-external: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.812534ms
      message: 'load-balancer-api-external: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 6.238636ms
      message: 'load-balancer-api-external: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 5.713312ms
      message: 'load-balancer-api-external: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 5.76703ms
      message: 'load-balancer-api-external: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 6.025866ms
      message: 'load-balancer-api-external: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 6.343093ms
      message: 'load-balancer-api-external: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 4.316353ms
      message: 'load-balancer-api-external: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 5.817744ms
      message: 'load-balancer-api-external: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 4.975076ms
      message: 'load-balancer-api-external: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:54:52Z"
    - latency: 5.785018ms
      message: 'load-balancer-api-external: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T19:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e5c5100b-93ff-4f1d-8a91-69a0205e747b
    resourceVersion: "39404"
    uid: e2bcc217-4508-4bf8-95c8-219924f997b6
  spec:
    sourcePod: network-check-source-7f44b6dd87-kxg9n
    targetEndpoint: a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T19:40:52Z"
      message: 'load-balancer-api-internal: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.993419ms
      message: 'load-balancer-api-internal: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 6.19219ms
      message: 'load-balancer-api-internal: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 5.669955ms
      message: 'load-balancer-api-internal: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 5.829937ms
      message: 'load-balancer-api-internal: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 6.002324ms
      message: 'load-balancer-api-internal: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 6.301382ms
      message: 'load-balancer-api-internal: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 4.916975ms
      message: 'load-balancer-api-internal: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 5.930658ms
      message: 'load-balancer-api-internal: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 5.018563ms
      message: 'load-balancer-api-internal: tcp connection to a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:54:52Z"
    - latency: 5.85197ms
      message: 'load-balancer-api-internal: resolved host name a4e71f067b63b49f0bd7c9f33f83f85c-d06a5f12dd7cbf3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T19:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-134-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e5c5100b-93ff-4f1d-8a91-69a0205e747b
    resourceVersion: "43537"
    uid: b0458123-ded5-4076-ba41-f60580269072
  spec:
    sourcePod: network-check-source-7f44b6dd87-kxg9n
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T19:41:52Z"
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.590234ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:02:52Z"
    - latency: 1.802943ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:01:52Z"
    - latency: 1.979475ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:00:52Z"
    - latency: 1.857787ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:59:52Z"
    - latency: 1.850676ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 2.235906ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 2.174204ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 2.364934ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 1.953212ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:54:52Z"
    - latency: 2.460771ms
      message: 'network-check-target-ip-10-0-134-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T19:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-139-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e5c5100b-93ff-4f1d-8a91-69a0205e747b
    resourceVersion: "43538"
    uid: d34d37f0-402a-47cb-989b-2801bbc03c9a
  spec:
    sourcePod: network-check-source-7f44b6dd87-kxg9n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T19:41:52Z"
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.867µs
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:02:52Z"
    - latency: 1.33177ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:01:52Z"
    - latency: 848.177µs
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:00:52Z"
    - latency: 1.200333ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:59:52Z"
    - latency: 706.621µs
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 1.382212ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 1.522523ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 1.467756ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 1.442093ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:54:52Z"
    - latency: 1.397504ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T19:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-140-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e5c5100b-93ff-4f1d-8a91-69a0205e747b
    resourceVersion: "43539"
    uid: a2e07e37-43f9-4733-9957-a88e8268ce17
  spec:
    sourcePod: network-check-source-7f44b6dd87-kxg9n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T19:41:52Z"
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.984369ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:02:52Z"
    - latency: 2.031089ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:01:52Z"
    - latency: 2.399921ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T20:00:52Z"
    - latency: 2.719435ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:59:52Z"
    - latency: 2.216523ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 2.290811ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 2.295565ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 2.393395ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 2.184692ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:54:52Z"
    - latency: 2.681506ms
      message: 'network-check-target-ip-10-0-140-240: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:53:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T19:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-51-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-51.ec2.internal
      uid: e5c5100b-93ff-4f1d-8a91-69a0205e747b
    resourceVersion: "39403"
    uid: 84c56fe9-b0de-405e-8fed-344210ea9425
  spec:
    sourcePod: network-check-source-7f44b6dd87-kxg9n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T19:40:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.783µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 1.571372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:58:52Z"
    - latency: 798.045µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 1.545875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:57:52Z"
    - latency: 1.047249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 1.806805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:56:52Z"
    - latency: 824.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 1.677993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:55:52Z"
    - latency: 979.496µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T19:54:52Z"
    - latency: 1.534191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T19:54:52Z"
kind: List
metadata:
  resourceVersion: ""