apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:44:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-253.ec2.internal
      uid: e3cba4f8-906b-4685-8ff7-02ac754b94d6
    resourceVersion: "45942"
    uid: 2a1f846b-9408-4d0b-ad66-b930a2934531
  spec:
    sourcePod: network-check-source-dbd9cf844-bhfc6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:51:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 1.048273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 1.097391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:10:43Z"
    - latency: 1.321863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:09:43Z"
    - latency: 1.117338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:08:43Z"
    - latency: 1.050437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:07:43Z"
    - latency: 1.032957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:06:43Z"
    - latency: 1.111445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:05:43Z"
    - latency: 1.192416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:04:43Z"
    - latency: 958.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:44:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-253.ec2.internal
      uid: e3cba4f8-906b-4685-8ff7-02ac754b94d6
    resourceVersion: "47754"
    uid: f882f4bd-b0f2-41ca-9f9f-2d72c00f7fb3
  spec:
    sourcePod: network-check-source-dbd9cf844-bhfc6
    targetEndpoint: a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:50:43Z"
      message: 'load-balancer-api-external: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.160043ms
      message: 'load-balancer-api-external: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:14:43Z"
    - latency: 6.648371ms
      message: 'load-balancer-api-external: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:14:43Z"
    - latency: 6.245525ms
      message: 'load-balancer-api-external: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:13:43Z"
    - latency: 7.025119ms
      message: 'load-balancer-api-external: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:13:43Z"
    - latency: 5.16866ms
      message: 'load-balancer-api-external: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 6.51621ms
      message: 'load-balancer-api-external: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 4.67155ms
      message: 'load-balancer-api-external: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 7.831288ms
      message: 'load-balancer-api-external: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 5.139124ms
      message: 'load-balancer-api-external: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:10:43Z"
    - latency: 10.944053ms
      message: 'load-balancer-api-external: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:10:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:44:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-253.ec2.internal
      uid: e3cba4f8-906b-4685-8ff7-02ac754b94d6
    resourceVersion: "47755"
    uid: e88216f3-6e97-4a08-80be-767e30263921
  spec:
    sourcePod: network-check-source-dbd9cf844-bhfc6
    targetEndpoint: a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:50:43Z"
      message: 'load-balancer-api-internal: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.008962ms
      message: 'load-balancer-api-internal: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:14:43Z"
    - latency: 6.623508ms
      message: 'load-balancer-api-internal: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:14:43Z"
    - latency: 6.946098ms
      message: 'load-balancer-api-internal: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:13:43Z"
    - latency: 7.049965ms
      message: 'load-balancer-api-internal: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:13:43Z"
    - latency: 5.132667ms
      message: 'load-balancer-api-internal: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 6.532092ms
      message: 'load-balancer-api-internal: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 3.976727ms
      message: 'load-balancer-api-internal: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 7.705459ms
      message: 'load-balancer-api-internal: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 5.187065ms
      message: 'load-balancer-api-internal: tcp connection to a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:10:43Z"
    - latency: 10.900449ms
      message: 'load-balancer-api-internal: resolved host name a0dab79d2370c487fab6a633503f6ba1-fd60df0434c69516.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:10:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:44:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-253-to-network-check-target-ip-10-0-136-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-253.ec2.internal
      uid: e3cba4f8-906b-4685-8ff7-02ac754b94d6
    resourceVersion: "45940"
    uid: d44460b3-d9c3-49c4-8375-703aa2fddb14
  spec:
    sourcePod: network-check-source-dbd9cf844-bhfc6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:51:43Z"
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.955509ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 2.226138ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 2.143605ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:10:43Z"
    - latency: 2.048077ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:09:43Z"
    - latency: 2.310853ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:08:43Z"
    - latency: 2.043771ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:07:43Z"
    - latency: 2.09438ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:06:43Z"
    - latency: 2.239362ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:05:43Z"
    - latency: 2.284451ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:04:43Z"
    - latency: 2.175758ms
      message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:44:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-253-to-network-check-target-ip-10-0-139-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-253.ec2.internal
      uid: e3cba4f8-906b-4685-8ff7-02ac754b94d6
    resourceVersion: "45939"
    uid: 13beeb79-1229-4715-9adf-615c3c6d1b8e
  spec:
    sourcePod: network-check-source-dbd9cf844-bhfc6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:51:43Z"
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023628ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 1.468154ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 1.541058ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:10:43Z"
    - latency: 970.342µs
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:09:43Z"
    - latency: 790.296µs
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:08:43Z"
    - latency: 882.178µs
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:07:43Z"
    - latency: 1.156463ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:06:43Z"
    - latency: 922.405µs
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:05:43Z"
    - latency: 803.178µs
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:04:43Z"
    - latency: 1.229882ms
      message: 'network-check-target-ip-10-0-139-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:44:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-253-to-network-check-target-ip-10-0-141-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-253.ec2.internal
      uid: e3cba4f8-906b-4685-8ff7-02ac754b94d6
    resourceVersion: "45941"
    uid: e1ebffbc-639f-4022-b531-3b1526dd0a08
  spec:
    sourcePod: network-check-source-dbd9cf844-bhfc6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:51:43Z"
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.014537ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 2.506015ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 2.195054ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:10:43Z"
    - latency: 2.347711ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:09:43Z"
    - latency: 2.352719ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:08:43Z"
    - latency: 2.340633ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:07:43Z"
    - latency: 2.226495ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:06:43Z"
    - latency: 2.248178ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:05:43Z"
    - latency: 2.664693ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:04:43Z"
    - latency: 2.364305ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:03:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:44:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-253.ec2.internal
      uid: e3cba4f8-906b-4685-8ff7-02ac754b94d6
    resourceVersion: "47753"
    uid: ba7b612c-0533-4672-ae85-349047a147bc
  spec:
    sourcePod: network-check-source-dbd9cf844-bhfc6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:50:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.721µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:14:43Z"
    - latency: 1.787146ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:14:43Z"
    - latency: 919.515µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:13:43Z"
    - latency: 1.660079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:13:43Z"
    - latency: 653.407µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 2.035777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:12:43Z"
    - latency: 955.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 2.523423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:11:43Z"
    - latency: 959.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T22:10:43Z"
    - latency: 1.915302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T22:10:43Z"
kind: List
metadata:
  resourceVersion: ""