apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:18:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: a3095fed-ce94-4a8c-bdeb-e6a660a2cfb0
    resourceVersion: "67097"
    uid: bbcff2b8-0128-4278-bcaa-ab151bbcfa9e
  spec:
    sourcePod: network-check-source-7cbc45fddc-8pjgd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:25:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 1.31608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 940.766µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 992.316µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:13Z"
    - latency: 1.143712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:13Z"
    - latency: 1.327338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:13Z"
    - latency: 950.278µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:13Z"
    - latency: 1.192609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:13Z"
    - latency: 1.011455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:13Z"
    - latency: 992.162µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:18:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: a3095fed-ce94-4a8c-bdeb-e6a660a2cfb0
    resourceVersion: "68046"
    uid: ff464716-1e86-4488-8bc6-7da676827998
  spec:
    sourcePod: network-check-source-7cbc45fddc-8pjgd
    targetEndpoint: a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:24:13Z"
      message: 'load-balancer-api-external: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.552922ms
      message: 'load-balancer-api-external: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:54:13Z"
    - latency: 8.944944ms
      message: 'load-balancer-api-external: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:54:13Z"
    - latency: 4.897123ms
      message: 'load-balancer-api-external: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 8.943836ms
      message: 'load-balancer-api-external: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 3.562076ms
      message: 'load-balancer-api-external: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 9.396915ms
      message: 'load-balancer-api-external: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 8.696907ms
      message: 'load-balancer-api-external: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 8.562857ms
      message: 'load-balancer-api-external: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 5.858465ms
      message: 'load-balancer-api-external: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:13Z"
    - latency: 7.861499ms
      message: 'load-balancer-api-external: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:50:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:18:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: a3095fed-ce94-4a8c-bdeb-e6a660a2cfb0
    resourceVersion: "68045"
    uid: c0c6bcef-ddda-4b29-92f6-fd79d0276b3b
  spec:
    sourcePod: network-check-source-7cbc45fddc-8pjgd
    targetEndpoint: a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:24:13Z"
      message: 'load-balancer-api-internal: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.821299ms
      message: 'load-balancer-api-internal: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:54:13Z"
    - latency: 9.032563ms
      message: 'load-balancer-api-internal: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:54:13Z"
    - latency: 4.913438ms
      message: 'load-balancer-api-internal: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 8.890214ms
      message: 'load-balancer-api-internal: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 4.353382ms
      message: 'load-balancer-api-internal: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 9.477241ms
      message: 'load-balancer-api-internal: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 3.75871ms
      message: 'load-balancer-api-internal: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 8.52442ms
      message: 'load-balancer-api-internal: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 5.819316ms
      message: 'load-balancer-api-internal: tcp connection to a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:13Z"
    - latency: 7.988534ms
      message: 'load-balancer-api-internal: resolved host name a2b90ac2434ec4e0eb5f234538521196-52b00f78747329a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:50:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:18:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-ip-10-0-128-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: a3095fed-ce94-4a8c-bdeb-e6a660a2cfb0
    resourceVersion: "67094"
    uid: 6c0cb0f9-63bb-4dc2-833a-4fed8fc1e96e
  spec:
    sourcePod: network-check-source-7cbc45fddc-8pjgd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:25:13Z"
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 832.325µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 825.805µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 875.857µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 964.545µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:13Z"
    - latency: 948.536µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:13Z"
    - latency: 762.169µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:13Z"
    - latency: 1.098565ms
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:13Z"
    - latency: 991.219µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:13Z"
    - latency: 837.617µs
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:13Z"
    - latency: 1.351424ms
      message: 'network-check-target-ip-10-0-128-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:18:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-ip-10-0-135-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: a3095fed-ce94-4a8c-bdeb-e6a660a2cfb0
    resourceVersion: "67096"
    uid: 172337f8-7849-4e6d-a73c-664025850ca3
  spec:
    sourcePod: network-check-source-7cbc45fddc-8pjgd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:25:13Z"
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.43856ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 2.310314ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 2.502477ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 2.434944ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:13Z"
    - latency: 2.216838ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:13Z"
    - latency: 2.42749ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:13Z"
    - latency: 2.035447ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:13Z"
    - latency: 2.192059ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:13Z"
    - latency: 2.288955ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:13Z"
    - latency: 2.078455ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:18:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-ip-10-0-139-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: a3095fed-ce94-4a8c-bdeb-e6a660a2cfb0
    resourceVersion: "67095"
    uid: baf559c7-6a3f-4746-be4f-2baa06e7baf0
  spec:
    sourcePod: network-check-source-7cbc45fddc-8pjgd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:25:13Z"
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.521302ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 2.079249ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 2.445603ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 2.352334ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:13Z"
    - latency: 2.206424ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:13Z"
    - latency: 2.517139ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:13Z"
    - latency: 2.53069ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:13Z"
    - latency: 2.435286ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:13Z"
    - latency: 2.224148ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:13Z"
    - latency: 2.702309ms
      message: 'network-check-target-ip-10-0-139-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:18:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-9.ec2.internal
      uid: a3095fed-ce94-4a8c-bdeb-e6a660a2cfb0
    resourceVersion: "68044"
    uid: 10415087-f76b-41d7-ac38-603410009cce
  spec:
    sourcePod: network-check-source-7cbc45fddc-8pjgd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:24:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 734.296µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:54:13Z"
    - latency: 1.82179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:54:13Z"
    - latency: 856.34µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 1.876196ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:53:13Z"
    - latency: 993.321µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 1.690708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:52:13Z"
    - latency: 815.541µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 1.861879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:51:13Z"
    - latency: 1.0546ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:13Z"
    - latency: 1.60011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:50:13Z"
kind: List
metadata:
  resourceVersion: ""