apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:49:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-94.ec2.internal
      uid: d0f073c1-5f1d-4604-9264-6a962f3e3cff
    resourceVersion: "67117"
    uid: 2a0491ab-1a4e-440a-a307-3208c1ad6445
  spec:
    sourcePod: network-check-source-7cbc45fddc-nqz29
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:56:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 1.175232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 1.028751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 1.056429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:21:17Z"
    - latency: 1.176722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:20:17Z"
    - latency: 1.407735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:19:17Z"
    - latency: 1.347627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:18:17Z"
    - latency: 1.212097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:17:17Z"
    - latency: 1.206271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:16:17Z"
    - latency: 980.99µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:15:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:49:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-94.ec2.internal
      uid: d0f073c1-5f1d-4604-9264-6a962f3e3cff
    resourceVersion: "67738"
    uid: 2100cc55-d1e6-4e0c-845a-2cbac21e448c
  spec:
    sourcePod: network-check-source-7cbc45fddc-nqz29
    targetEndpoint: a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:55:17Z"
      message: 'load-balancer-api-external: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.970086ms
      message: 'load-balancer-api-external: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:25:17Z"
    - latency: 7.223898ms
      message: 'load-balancer-api-external: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:25:17Z"
    - latency: 5.44243ms
      message: 'load-balancer-api-external: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 7.354563ms
      message: 'load-balancer-api-external: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 5.767294ms
      message: 'load-balancer-api-external: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 7.081793ms
      message: 'load-balancer-api-external: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 3.744368ms
      message: 'load-balancer-api-external: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 7.574753ms
      message: 'load-balancer-api-external: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 3.532623ms
      message: 'load-balancer-api-external: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:21:17Z"
    - latency: 6.987397ms
      message: 'load-balancer-api-external: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:21:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:49:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-94.ec2.internal
      uid: d0f073c1-5f1d-4604-9264-6a962f3e3cff
    resourceVersion: "67737"
    uid: bd55ba08-c101-488c-94cf-cf0a32004668
  spec:
    sourcePod: network-check-source-7cbc45fddc-nqz29
    targetEndpoint: a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:55:17Z"
      message: 'load-balancer-api-internal: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.012378ms
      message: 'load-balancer-api-internal: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:25:17Z"
    - latency: 7.139517ms
      message: 'load-balancer-api-internal: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:25:17Z"
    - latency: 5.664563ms
      message: 'load-balancer-api-internal: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 7.375313ms
      message: 'load-balancer-api-internal: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 3.826777ms
      message: 'load-balancer-api-internal: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 7.025921ms
      message: 'load-balancer-api-internal: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 5.027282ms
      message: 'load-balancer-api-internal: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 7.565674ms
      message: 'load-balancer-api-internal: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 6.394674ms
      message: 'load-balancer-api-internal: tcp connection to a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:21:17Z"
    - latency: 7.03308ms
      message: 'load-balancer-api-internal: resolved host name a9520980d98354a7282d063dbb2ff70a-deffc0938e9c7a62.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:21:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:49:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-94-to-network-check-target-ip-10-0-132-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-94.ec2.internal
      uid: d0f073c1-5f1d-4604-9264-6a962f3e3cff
    resourceVersion: "67115"
    uid: aefc0577-59dd-4d61-9bd6-089c2ffeab99
  spec:
    sourcePod: network-check-source-7cbc45fddc-nqz29
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:56:17Z"
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.528622ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 2.384963ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 2.412349ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 2.267132ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:21:17Z"
    - latency: 2.060796ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:20:17Z"
    - latency: 2.295868ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:19:17Z"
    - latency: 2.561916ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:18:17Z"
    - latency: 2.63171ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:17:17Z"
    - latency: 2.399774ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:16:17Z"
    - latency: 2.613385ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:15:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:49:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-94-to-network-check-target-ip-10-0-132-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-94.ec2.internal
      uid: d0f073c1-5f1d-4604-9264-6a962f3e3cff
    resourceVersion: "67114"
    uid: df259960-9e98-461e-a98b-8ec4bc18f64f
  spec:
    sourcePod: network-check-source-7cbc45fddc-nqz29
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:56:17Z"
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.677513ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 1.028341ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 1.031046ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 1.394479ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:21:17Z"
    - latency: 1.15048ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:20:17Z"
    - latency: 1.10082ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:19:17Z"
    - latency: 1.427219ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:18:17Z"
    - latency: 1.046145ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:17:17Z"
    - latency: 1.442899ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:16:17Z"
    - latency: 1.078475ms
      message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:15:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:49:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-94-to-network-check-target-ip-10-0-136-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-94.ec2.internal
      uid: d0f073c1-5f1d-4604-9264-6a962f3e3cff
    resourceVersion: "67116"
    uid: 3108c4ac-a8bd-4d10-a106-1ac51f9335d2
  spec:
    sourcePod: network-check-source-7cbc45fddc-nqz29
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:56:17Z"
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.690078ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 2.048262ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 2.453629ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 2.534685ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:21:17Z"
    - latency: 3.280519ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:20:17Z"
    - latency: 2.895605ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:19:17Z"
    - latency: 2.716593ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:18:17Z"
    - latency: 2.640138ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:17:17Z"
    - latency: 2.628373ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:16:17Z"
    - latency: 2.586143ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:15:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:49:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-94.ec2.internal
      uid: d0f073c1-5f1d-4604-9264-6a962f3e3cff
    resourceVersion: "67736"
    uid: 0f38c49c-5050-4ce0-a872-cffdcabf7e44
  spec:
    sourcePod: network-check-source-7cbc45fddc-nqz29
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:55:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.72µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:25:17Z"
    - latency: 1.919756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:25:17Z"
    - latency: 1.423528ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 2.080444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:24:17Z"
    - latency: 1.124099ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 1.742576ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:23:17Z"
    - latency: 843.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 2.561618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:22:17Z"
    - latency: 1.035138ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:21:17Z"
    - latency: 1.804527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T19:21:17Z"
kind: List
metadata:
  resourceVersion: ""