apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T00:34:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-178.ec2.internal
      uid: 3ee74912-01ae-4160-8949-f518793e4f6d
    resourceVersion: "64761"
    uid: 01b8537f-5059-4cfd-9346-bb3feece83c0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-b522z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T00:41:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.303799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 1.200952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 1.102452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 1.21263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 1.469259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:12:29Z"
    - latency: 803.94µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:11:29Z"
    - latency: 993.523µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:10:29Z"
    - latency: 1.060395ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:09:29Z"
    - latency: 939.932µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:08:29Z"
    - latency: 1.22003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T00:34:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-178.ec2.internal
      uid: 3ee74912-01ae-4160-8949-f518793e4f6d
    resourceVersion: "64763"
    uid: fba9f50b-e19b-429b-b5e8-e72f49897aa6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-b522z
    targetEndpoint: a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T00:40:29Z"
      message: 'load-balancer-api-external: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.831939ms
      message: 'load-balancer-api-external: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 9.22116ms
      message: 'load-balancer-api-external: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 5.623304ms
      message: 'load-balancer-api-external: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 8.662617ms
      message: 'load-balancer-api-external: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 9.78573ms
      message: 'load-balancer-api-external: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 8.757174ms
      message: 'load-balancer-api-external: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 5.415252ms
      message: 'load-balancer-api-external: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 8.691232ms
      message: 'load-balancer-api-external: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 5.304828ms
      message: 'load-balancer-api-external: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:12:29Z"
    - latency: 9.251704ms
      message: 'load-balancer-api-external: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:12:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T00:34:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-178.ec2.internal
      uid: 3ee74912-01ae-4160-8949-f518793e4f6d
    resourceVersion: "64765"
    uid: 4a89d90b-7f3c-4818-9f78-f81d33f52418
  spec:
    sourcePod: network-check-source-7bc5b6bf85-b522z
    targetEndpoint: a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T00:40:29Z"
      message: 'load-balancer-api-internal: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.495014ms
      message: 'load-balancer-api-internal: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 9.302838ms
      message: 'load-balancer-api-internal: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 4.852949ms
      message: 'load-balancer-api-internal: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 8.754593ms
      message: 'load-balancer-api-internal: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 5.644426ms
      message: 'load-balancer-api-internal: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 8.694471ms
      message: 'load-balancer-api-internal: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 5.407303ms
      message: 'load-balancer-api-internal: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 8.960397ms
      message: 'load-balancer-api-internal: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 3.748223ms
      message: 'load-balancer-api-internal: tcp connection to a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:12:29Z"
    - latency: 9.206597ms
      message: 'load-balancer-api-internal: resolved host name a8cf086149fdc4b0a96470aba2a80c15-fa3d1c29f50721e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:12:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T00:34:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-178-to-network-check-target-ip-10-0-131-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-178.ec2.internal
      uid: 3ee74912-01ae-4160-8949-f518793e4f6d
    resourceVersion: "64760"
    uid: 2bcee692-b5dc-4168-af66-c13e471276af
  spec:
    sourcePod: network-check-source-7bc5b6bf85-b522z
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T00:41:29Z"
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.903759ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 1.912345ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 1.953251ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 1.928079ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 1.901358ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:12:29Z"
    - latency: 2.038978ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:11:29Z"
    - latency: 2.05313ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:10:29Z"
    - latency: 2.572319ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:09:29Z"
    - latency: 1.941736ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:08:29Z"
    - latency: 1.95213ms
      message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T00:34:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-178-to-network-check-target-ip-10-0-132-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-178.ec2.internal
      uid: 3ee74912-01ae-4160-8949-f518793e4f6d
    resourceVersion: "64757"
    uid: f6727e14-7a20-45d1-bd6d-6e7692c91e65
  spec:
    sourcePod: network-check-source-7bc5b6bf85-b522z
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T00:41:29Z"
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.297521ms
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 1.104135ms
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 875.293µs
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 870.126µs
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 898.122µs
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:12:29Z"
    - latency: 1.60866ms
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:11:29Z"
    - latency: 871.112µs
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:10:29Z"
    - latency: 1.54538ms
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:09:29Z"
    - latency: 1.29257ms
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:08:29Z"
    - latency: 977.69µs
      message: 'network-check-target-ip-10-0-132-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T00:34:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-178-to-network-check-target-ip-10-0-139-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-178.ec2.internal
      uid: 3ee74912-01ae-4160-8949-f518793e4f6d
    resourceVersion: "64758"
    uid: 59a6cab0-beee-48de-986d-cd68e6611fc6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-b522z
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T00:41:29Z"
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.1912ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 2.162507ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 2.207001ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 2.105705ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 2.268417ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:12:29Z"
    - latency: 2.104572ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:11:29Z"
    - latency: 2.128626ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:10:29Z"
    - latency: 2.580174ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:09:29Z"
    - latency: 2.135853ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:08:29Z"
    - latency: 2.246101ms
      message: 'network-check-target-ip-10-0-139-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T00:34:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-178.ec2.internal
      uid: 3ee74912-01ae-4160-8949-f518793e4f6d
    resourceVersion: "64759"
    uid: 22fe3e23-fde1-4cf3-9779-0ea57a11500a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-b522z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T00:40:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.07311ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 1.848172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:16:29Z"
    - latency: 937.967µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 2.126117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:15:29Z"
    - latency: 928.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 1.857088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:14:29Z"
    - latency: 840.912µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 2.117342ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:13:29Z"
    - latency: 848.14µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T01:12:29Z"
    - latency: 2.331418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T01:12:29Z"
kind: List
metadata:
  resourceVersion: ""