apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 3a249059-832e-43ad-ae7f-700dc970492a
    resourceVersion: "27755"
    uid: bd9b76f4-830c-47ed-8952-e662f5080c0f
  spec:
    sourcePod: network-check-source-cc88fdd44-2v9sz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.89µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 985.379µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 1.068217ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 931.581µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 961.132µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:28:08Z"
    - latency: 1.003914ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:27:08Z"
    - latency: 1.006873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:26:08Z"
    - latency: 1.007865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:25:08Z"
    - latency: 1.20947ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:24:08Z"
    - latency: 951.152µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:23:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 3a249059-832e-43ad-ae7f-700dc970492a
    resourceVersion: "27756"
    uid: 24f96e9c-74b5-42f2-bf76-c365c07d025b
  spec:
    sourcePod: network-check-source-cc88fdd44-2v9sz
    targetEndpoint: a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:56:08Z"
      message: 'load-balancer-api-external: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.598773ms
      message: 'load-balancer-api-external: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 6.040261ms
      message: 'load-balancer-api-external: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 3.967774ms
      message: 'load-balancer-api-external: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 6.256595ms
      message: 'load-balancer-api-external: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 4.84744ms
      message: 'load-balancer-api-external: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 7.90306ms
      message: 'load-balancer-api-external: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 5.497889ms
      message: 'load-balancer-api-external: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 7.037153ms
      message: 'load-balancer-api-external: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 5.723181ms
      message: 'load-balancer-api-external: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:28:08Z"
    - latency: 6.286521ms
      message: 'load-balancer-api-external: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:28:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 3a249059-832e-43ad-ae7f-700dc970492a
    resourceVersion: "27757"
    uid: c7984a3c-5e14-44af-997e-27eb55f77815
  spec:
    sourcePod: network-check-source-cc88fdd44-2v9sz
    targetEndpoint: a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:56:08Z"
      message: 'load-balancer-api-internal: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.623972ms
      message: 'load-balancer-api-internal: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 6.009895ms
      message: 'load-balancer-api-internal: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 4.001351ms
      message: 'load-balancer-api-internal: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 6.205763ms
      message: 'load-balancer-api-internal: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 4.519186ms
      message: 'load-balancer-api-internal: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 7.911033ms
      message: 'load-balancer-api-internal: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 5.666061ms
      message: 'load-balancer-api-internal: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 7.005809ms
      message: 'load-balancer-api-internal: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 5.543507ms
      message: 'load-balancer-api-internal: tcp connection to a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:28:08Z"
    - latency: 6.249329ms
      message: 'load-balancer-api-internal: resolved host name a98aed838a3c24383ab1f8da9c92b970-b43c3cd2d6848656.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:28:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-139-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 3a249059-832e-43ad-ae7f-700dc970492a
    resourceVersion: "27754"
    uid: 54c8c674-869e-4625-8c77-52567c0ec670
  spec:
    sourcePod: network-check-source-cc88fdd44-2v9sz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:08Z"
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.913721ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 1.978621ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 2.042841ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 1.938801ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 1.977888ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:28:08Z"
    - latency: 1.96288ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:27:08Z"
    - latency: 2.005808ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:26:08Z"
    - latency: 1.933586ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:25:08Z"
    - latency: 2.099146ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:24:08Z"
    - latency: 2.050397ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:23:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-141-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 3a249059-832e-43ad-ae7f-700dc970492a
    resourceVersion: "27752"
    uid: 30fb427f-d866-427f-9154-946ad506c166
  spec:
    sourcePod: network-check-source-cc88fdd44-2v9sz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:08Z"
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.109354ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 2.232705ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 2.093482ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 2.24391ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 2.264773ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:28:08Z"
    - latency: 2.079637ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:27:08Z"
    - latency: 2.01293ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:26:08Z"
    - latency: 2.085137ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:25:08Z"
    - latency: 2.03387ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:24:08Z"
    - latency: 1.862895ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:23:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-143-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 3a249059-832e-43ad-ae7f-700dc970492a
    resourceVersion: "27751"
    uid: 6d23dff7-d1d7-4975-a495-b8146fe7ca68
  spec:
    sourcePod: network-check-source-cc88fdd44-2v9sz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:08Z"
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016024ms
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 891.032µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 879.893µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 938.245µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 1.001633ms
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:28:08Z"
    - latency: 767.378µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:27:08Z"
    - latency: 777.941µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:26:08Z"
    - latency: 924.572µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:25:08Z"
    - latency: 836.412µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:24:08Z"
    - latency: 878.507µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:23:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 3a249059-832e-43ad-ae7f-700dc970492a
    resourceVersion: "27753"
    uid: 52041989-1ae2-4e99-b51c-4382d109b5fa
  spec:
    sourcePod: network-check-source-cc88fdd44-2v9sz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:56:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.164518ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 1.69718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:32:08Z"
    - latency: 770.073µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 1.735458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:31:08Z"
    - latency: 985.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 1.66082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:30:08Z"
    - latency: 1.162196ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 1.873452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:29:08Z"
    - latency: 778.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T17:28:08Z"
    - latency: 1.767783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T17:28:08Z"
kind: List
metadata:
  resourceVersion: ""