apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-78.ec2.internal
      uid: 03e3ac02-746e-474a-9eca-3901364c132a
    resourceVersion: "34573"
    uid: f33ed0ae-2fbc-425b-9ef6-fa3eeb3b2d21
  spec:
    sourcePod: network-check-source-7b678d77c7-8hbqw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:12:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.222949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 1.280648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 984.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:31:11Z"
    - latency: 1.225373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:30:11Z"
    - latency: 859.706µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:29:11Z"
    - latency: 1.067356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:28:11Z"
    - latency: 1.263775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:27:11Z"
    - latency: 1.145968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:26:11Z"
    - latency: 1.080069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:25:11Z"
    - latency: 875.464µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:24:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-78.ec2.internal
      uid: 03e3ac02-746e-474a-9eca-3901364c132a
    resourceVersion: "36708"
    uid: 3a157c5f-eb73-4d3c-a020-d4158e0a2c0b
  spec:
    sourcePod: network-check-source-7b678d77c7-8hbqw
    targetEndpoint: a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:11:11Z"
      message: 'load-balancer-api-external: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.673181ms
      message: 'load-balancer-api-external: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:35:11Z"
    - latency: 7.817286ms
      message: 'load-balancer-api-external: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:35:11Z"
    - latency: 5.23268ms
      message: 'load-balancer-api-external: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:34:11Z"
    - latency: 9.301526ms
      message: 'load-balancer-api-external: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:34:11Z"
    - latency: 4.604458ms
      message: 'load-balancer-api-external: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 7.203998ms
      message: 'load-balancer-api-external: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 5.464601ms
      message: 'load-balancer-api-external: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 7.437073ms
      message: 'load-balancer-api-external: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 4.438083ms
      message: 'load-balancer-api-external: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:31:11Z"
    - latency: 8.814004ms
      message: 'load-balancer-api-external: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-78.ec2.internal
      uid: 03e3ac02-746e-474a-9eca-3901364c132a
    resourceVersion: "36709"
    uid: e6b1c5e9-51b5-494c-bfa8-cf6659dc42ab
  spec:
    sourcePod: network-check-source-7b678d77c7-8hbqw
    targetEndpoint: a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:11:11Z"
      message: 'load-balancer-api-internal: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.66453ms
      message: 'load-balancer-api-internal: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:35:11Z"
    - latency: 7.948658ms
      message: 'load-balancer-api-internal: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:35:11Z"
    - latency: 5.237043ms
      message: 'load-balancer-api-internal: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:34:11Z"
    - latency: 9.380315ms
      message: 'load-balancer-api-internal: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:34:11Z"
    - latency: 3.907687ms
      message: 'load-balancer-api-internal: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 7.34164ms
      message: 'load-balancer-api-internal: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 5.457032ms
      message: 'load-balancer-api-internal: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 7.062447ms
      message: 'load-balancer-api-internal: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 6.09176ms
      message: 'load-balancer-api-internal: tcp connection to a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:31:11Z"
    - latency: 8.940182ms
      message: 'load-balancer-api-internal: resolved host name a563ff9709f3145e99fbe23567ae45bb-a6c1a017050e67c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:31:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-78-to-network-check-target-ip-10-0-131-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-78.ec2.internal
      uid: 03e3ac02-746e-474a-9eca-3901364c132a
    resourceVersion: "34571"
    uid: 1ecaf024-1417-4c6d-b829-368596544d7d
  spec:
    sourcePod: network-check-source-7b678d77c7-8hbqw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:12:11Z"
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.919146ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 2.058978ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 1.915308ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:31:11Z"
    - latency: 1.947446ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:30:11Z"
    - latency: 2.251036ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:29:11Z"
    - latency: 1.764054ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:28:11Z"
    - latency: 2.318629ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:27:11Z"
    - latency: 1.881473ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:26:11Z"
    - latency: 1.851033ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:25:11Z"
    - latency: 2.249538ms
      message: 'network-check-target-ip-10-0-131-24: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:24:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-78-to-network-check-target-ip-10-0-134-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-78.ec2.internal
      uid: 03e3ac02-746e-474a-9eca-3901364c132a
    resourceVersion: "34572"
    uid: 98bf28b2-d28b-4da5-a60b-dcf3b337ba56
  spec:
    sourcePod: network-check-source-7b678d77c7-8hbqw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:12:11Z"
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.089523ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 2.843668ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 1.928222ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:31:11Z"
    - latency: 2.538965ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:30:11Z"
    - latency: 2.430277ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:29:11Z"
    - latency: 2.095156ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:28:11Z"
    - latency: 2.331417ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:27:11Z"
    - latency: 2.331249ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:26:11Z"
    - latency: 2.306542ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:25:11Z"
    - latency: 2.027033ms
      message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:24:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-78-to-network-check-target-ip-10-0-140-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-78.ec2.internal
      uid: 03e3ac02-746e-474a-9eca-3901364c132a
    resourceVersion: "34570"
    uid: b7cb6f5b-906d-455d-b786-3bccd9ec9b9c
  spec:
    sourcePod: network-check-source-7b678d77c7-8hbqw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:12:11Z"
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.191371ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 969.41µs
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 911.611µs
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:31:11Z"
    - latency: 833.278µs
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:30:11Z"
    - latency: 1.268012ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:29:11Z"
    - latency: 887.732µs
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:28:11Z"
    - latency: 1.390527ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:27:11Z"
    - latency: 988.15µs
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:26:11Z"
    - latency: 928.35µs
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:25:11Z"
    - latency: 1.052038ms
      message: 'network-check-target-ip-10-0-140-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:24:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T16:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-78.ec2.internal
      uid: 03e3ac02-746e-474a-9eca-3901364c132a
    resourceVersion: "36707"
    uid: 712dc766-38ba-4886-996d-6509dd98a9a7
  spec:
    sourcePod: network-check-source-7b678d77c7-8hbqw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T16:11:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.522µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:35:11Z"
    - latency: 1.999531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:35:11Z"
    - latency: 1.079182ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:34:11Z"
    - latency: 1.714505ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:34:11Z"
    - latency: 1.168681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 1.716921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:33:11Z"
    - latency: 907.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 1.62909ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:32:11Z"
    - latency: 974.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T16:31:11Z"
    - latency: 1.674242ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T16:31:11Z"
kind: List
metadata:
  resourceVersion: ""