apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-01T21:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-216-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-216.ec2.internal
      uid: 5102c5de-433e-403c-b071-8ead9e2a9ddb
    resourceVersion: "38833"
    uid: 5f26a8bb-4457-4229-885a-132fe38ec738
  spec:
    sourcePod: network-check-source-56d84b9f44-vjps7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-01T21:53:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.167211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 1.200462ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 890.98µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:12:46Z"
    - latency: 980.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:11:46Z"
    - latency: 917.818µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:10:46Z"
    - latency: 1.037729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:09:46Z"
    - latency: 1.142178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:08:46Z"
    - latency: 909.103µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:07:46Z"
    - latency: 1.174208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:06:46Z"
    - latency: 1.195109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-01T21:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-216-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-216.ec2.internal
      uid: 5102c5de-433e-403c-b071-8ead9e2a9ddb
    resourceVersion: "40791"
    uid: ea7368c5-eef0-4507-8034-722a6fb4718b
  spec:
    sourcePod: network-check-source-56d84b9f44-vjps7
    targetEndpoint: a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-01T21:52:46Z"
      message: 'load-balancer-api-external: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.872212ms
      message: 'load-balancer-api-external: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:16:46Z"
    - latency: 6.896452ms
      message: 'load-balancer-api-external: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:16:46Z"
    - latency: 5.227165ms
      message: 'load-balancer-api-external: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:15:46Z"
    - latency: 11.602232ms
      message: 'load-balancer-api-external: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:15:46Z"
    - latency: 4.591972ms
      message: 'load-balancer-api-external: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 7.00013ms
      message: 'load-balancer-api-external: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 3.96388ms
      message: 'load-balancer-api-external: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 6.946098ms
      message: 'load-balancer-api-external: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 4.742313ms
      message: 'load-balancer-api-external: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:12:46Z"
    - latency: 6.773904ms
      message: 'load-balancer-api-external: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-01T21:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-216-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-216.ec2.internal
      uid: 5102c5de-433e-403c-b071-8ead9e2a9ddb
    resourceVersion: "40792"
    uid: c1eb5777-862d-4408-be14-67d04584ca70
  spec:
    sourcePod: network-check-source-56d84b9f44-vjps7
    targetEndpoint: a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-01T21:52:46Z"
      message: 'load-balancer-api-internal: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.884499ms
      message: 'load-balancer-api-internal: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:16:46Z"
    - latency: 6.924753ms
      message: 'load-balancer-api-internal: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:16:46Z"
    - latency: 5.256085ms
      message: 'load-balancer-api-internal: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:15:46Z"
    - latency: 11.568718ms
      message: 'load-balancer-api-internal: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:15:46Z"
    - latency: 4.6753ms
      message: 'load-balancer-api-internal: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 6.964043ms
      message: 'load-balancer-api-internal: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 4.859727ms
      message: 'load-balancer-api-internal: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 7.008054ms
      message: 'load-balancer-api-internal: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 4.732836ms
      message: 'load-balancer-api-internal: tcp connection to a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:12:46Z"
    - latency: 6.828601ms
      message: 'load-balancer-api-internal: resolved host name a483048a433764965a4f4a2b4a141366-8bdd0af7bded04b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-01T21:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-216-to-network-check-target-ip-10-0-134-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-216.ec2.internal
      uid: 5102c5de-433e-403c-b071-8ead9e2a9ddb
    resourceVersion: "38830"
    uid: 38ed2669-4073-4e2b-a996-2ebf19bf429a
  spec:
    sourcePod: network-check-source-56d84b9f44-vjps7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-01T21:53:46Z"
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.994327ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 1.700922ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 1.740939ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:12:46Z"
    - latency: 1.839825ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:11:46Z"
    - latency: 1.62048ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:10:46Z"
    - latency: 2.038531ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:09:46Z"
    - latency: 1.842572ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:08:46Z"
    - latency: 1.760088ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:07:46Z"
    - latency: 1.763702ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:06:46Z"
    - latency: 1.966883ms
      message: 'network-check-target-ip-10-0-134-181: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-01T21:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-216-to-network-check-target-ip-10-0-137-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-216.ec2.internal
      uid: 5102c5de-433e-403c-b071-8ead9e2a9ddb
    resourceVersion: "38831"
    uid: bb1ae6fd-8987-42a7-8f47-bfbb0f9e21ce
  spec:
    sourcePod: network-check-source-56d84b9f44-vjps7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-01T21:53:46Z"
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.401209ms
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 1.061422ms
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 780.721µs
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:12:46Z"
    - latency: 1.373407ms
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:11:46Z"
    - latency: 819.93µs
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:10:46Z"
    - latency: 1.018028ms
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:09:46Z"
    - latency: 774.858µs
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:08:46Z"
    - latency: 1.473022ms
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:07:46Z"
    - latency: 1.013664ms
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:06:46Z"
    - latency: 802.158µs
      message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-01T21:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-216-to-network-check-target-ip-10-0-138-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-216.ec2.internal
      uid: 5102c5de-433e-403c-b071-8ead9e2a9ddb
    resourceVersion: "38832"
    uid: 47ef29a8-ddba-4707-a821-c982c5dcb92c
  spec:
    sourcePod: network-check-source-56d84b9f44-vjps7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-01T21:53:46Z"
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.127785ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 2.039048ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 1.999104ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:12:46Z"
    - latency: 2.173645ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:11:46Z"
    - latency: 1.911133ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:10:46Z"
    - latency: 2.207651ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:09:46Z"
    - latency: 2.288143ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:08:46Z"
    - latency: 2.090206ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:07:46Z"
    - latency: 1.96009ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:06:46Z"
    - latency: 2.122784ms
      message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-01T21:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-216-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-216.ec2.internal
      uid: 5102c5de-433e-403c-b071-8ead9e2a9ddb
    resourceVersion: "40790"
    uid: 7db2fec2-7f4c-449d-ae9a-ac7b0e189003
  spec:
    sourcePod: network-check-source-56d84b9f44-vjps7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-01T21:52:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.851µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:16:46Z"
    - latency: 2.135209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:16:46Z"
    - latency: 1.26877ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:15:46Z"
    - latency: 1.68091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:15:46Z"
    - latency: 908.926µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 1.87445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:14:46Z"
    - latency: 856.635µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 1.699819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:13:46Z"
    - latency: 788.819µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-01T22:12:46Z"
    - latency: 2.041634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-01T22:12:46Z"
kind: List
metadata:
  resourceVersion: ""