apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:57:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: df575bce-3583-48c0-b241-925e567588f4
    resourceVersion: "33360"
    uid: ff1ee8e8-4efb-41e1-b2f1-2743e3bdbb78
  spec:
    sourcePod: network-check-source-8894fc9bd-2t94g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:04:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.051773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:46:03Z"
    - latency: 1.196348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:45:03Z"
    - latency: 1.083032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:44:03Z"
    - latency: 1.045978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:43:03Z"
    - latency: 954.501µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:42:03Z"
    - latency: 1.133421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:41:03Z"
    - latency: 977.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:40:03Z"
    - latency: 822.252µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:39:03Z"
    - latency: 1.041168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:38:03Z"
    - latency: 1.085976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:57:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: df575bce-3583-48c0-b241-925e567588f4
    resourceVersion: "35476"
    uid: 148d09c3-6001-473c-8375-2d55192d9937
  spec:
    sourcePod: network-check-source-8894fc9bd-2t94g
    targetEndpoint: a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:03:03Z"
      message: 'load-balancer-api-external: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.060944ms
      message: 'load-balancer-api-external: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 9.210368ms
      message: 'load-balancer-api-external: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 4.256875ms
      message: 'load-balancer-api-external: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:50:03Z"
    - latency: 8.168706ms
      message: 'load-balancer-api-external: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:50:03Z"
    - latency: 4.728054ms
      message: 'load-balancer-api-external: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:49:03Z"
    - latency: 7.509205ms
      message: 'load-balancer-api-external: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:49:03Z"
    - latency: 4.166159ms
      message: 'load-balancer-api-external: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:48:03Z"
    - latency: 7.76576ms
      message: 'load-balancer-api-external: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:48:03Z"
    - latency: 2.651467ms
      message: 'load-balancer-api-external: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:47:03Z"
    - latency: 8.608916ms
      message: 'load-balancer-api-external: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:57:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: df575bce-3583-48c0-b241-925e567588f4
    resourceVersion: "35477"
    uid: 86038581-3c68-4c7e-abb4-c61f7afac6ab
  spec:
    sourcePod: network-check-source-8894fc9bd-2t94g
    targetEndpoint: a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:03:03Z"
      message: 'load-balancer-api-internal: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.479802ms
      message: 'load-balancer-api-internal: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 9.275816ms
      message: 'load-balancer-api-internal: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 4.237808ms
      message: 'load-balancer-api-internal: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:50:03Z"
    - latency: 8.136184ms
      message: 'load-balancer-api-internal: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:50:03Z"
    - latency: 4.356057ms
      message: 'load-balancer-api-internal: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:49:03Z"
    - latency: 7.587276ms
      message: 'load-balancer-api-internal: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:49:03Z"
    - latency: 3.637947ms
      message: 'load-balancer-api-internal: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:48:03Z"
    - latency: 7.778083ms
      message: 'load-balancer-api-internal: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:48:03Z"
    - latency: 2.722246ms
      message: 'load-balancer-api-internal: tcp connection to a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:47:03Z"
    - latency: 8.52907ms
      message: 'load-balancer-api-internal: resolved host name a10ff4bc5de194b44b9557ad720df9af-c9e3b73eadea2245.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:59:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-130-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: df575bce-3583-48c0-b241-925e567588f4
    resourceVersion: "34323"
    uid: f287628c-f32e-48f1-b17c-1e4ee36b7695
  spec:
    sourcePod: network-check-source-8894fc9bd-2t94g
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:06:26Z"
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.868612ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:48:26Z"
    - latency: 2.324167ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:47:26Z"
    - latency: 1.994131ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:46:26Z"
    - latency: 2.142145ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:45:26Z"
    - latency: 1.929841ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:44:26Z"
    - latency: 2.124499ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:43:26Z"
    - latency: 1.843273ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:42:26Z"
    - latency: 2.105897ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:41:26Z"
    - latency: 1.861352ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:40:26Z"
    - latency: 2.03239ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:39:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:57:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-142-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: df575bce-3583-48c0-b241-925e567588f4
    resourceVersion: "33358"
    uid: 38a60cae-df90-47aa-aaf9-ca9dcaa9fa8b
  spec:
    sourcePod: network-check-source-8894fc9bd-2t94g
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:04:03Z"
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.285273ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:46:03Z"
    - latency: 1.090472ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:45:03Z"
    - latency: 822.732µs
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:44:03Z"
    - latency: 1.296582ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:43:03Z"
    - latency: 1.120368ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:42:03Z"
    - latency: 1.536508ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:41:03Z"
    - latency: 870.688µs
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:40:03Z"
    - latency: 683.322µs
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:39:03Z"
    - latency: 838.782µs
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:38:03Z"
    - latency: 953.548µs
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:57:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-143-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: df575bce-3583-48c0-b241-925e567588f4
    resourceVersion: "33359"
    uid: bf956046-e81a-4736-82da-93056cc23e7e
  spec:
    sourcePod: network-check-source-8894fc9bd-2t94g
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:04:03Z"
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.259946ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:46:03Z"
    - latency: 2.215112ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:45:03Z"
    - latency: 2.280167ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:44:03Z"
    - latency: 1.865157ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:43:03Z"
    - latency: 2.414545ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:42:03Z"
    - latency: 2.192683ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:41:03Z"
    - latency: 2.048332ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:40:03Z"
    - latency: 2.334761ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:39:03Z"
    - latency: 2.264926ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:38:03Z"
    - latency: 2.513848ms
      message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T17:57:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: df575bce-3583-48c0-b241-925e567588f4
    resourceVersion: "35475"
    uid: c74482d7-d303-47f8-b320-dc7aa6099f2d
  spec:
    sourcePod: network-check-source-8894fc9bd-2t94g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T18:03:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.300326ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 1.591657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:51:03Z"
    - latency: 722.221µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:50:03Z"
    - latency: 1.680652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:50:03Z"
    - latency: 2.177949ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:49:03Z"
    - latency: 1.636672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:49:03Z"
    - latency: 869.55µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:48:03Z"
    - latency: 1.672606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:48:03Z"
    - latency: 889.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T18:47:03Z"
    - latency: 1.911201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T18:47:03Z"
kind: List
metadata:
  resourceVersion: ""