apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-167-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-167.ec2.internal
      uid: b11d8dcb-0eda-47bb-aeb4-080b493a977e
    resourceVersion: "31084"
    uid: dbdd4f6b-d3c3-4ec8-9b85-0434680d6180
  spec:
    sourcePod: network-check-source-dbd9cf844-f2wfw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:34:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.172148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:41:35Z"
    - latency: 1.040397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:40:35Z"
    - latency: 1.424319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 1.139785ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 851.786µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 1.255265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 982.228µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:35:35Z"
    - latency: 1.199043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:34:35Z"
    - latency: 985.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:33:35Z"
    - latency: 981.324µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:32:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-167-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-167.ec2.internal
      uid: b11d8dcb-0eda-47bb-aeb4-080b493a977e
    resourceVersion: "29827"
    uid: 8afd5169-594d-4341-8234-497cc7e0657f
  spec:
    sourcePod: network-check-source-dbd9cf844-f2wfw
    targetEndpoint: ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:33:35Z"
      message: 'load-balancer-api-external: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.085868ms
      message: 'load-balancer-api-external: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 8.578203ms
      message: 'load-balancer-api-external: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 4.835523ms
      message: 'load-balancer-api-external: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 9.601955ms
      message: 'load-balancer-api-external: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 4.422618ms
      message: 'load-balancer-api-external: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 9.312276ms
      message: 'load-balancer-api-external: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 5.892138ms
      message: 'load-balancer-api-external: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 9.633962ms
      message: 'load-balancer-api-external: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 6.634961ms
      message: 'load-balancer-api-external: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:35:35Z"
    - latency: 8.397825ms
      message: 'load-balancer-api-external: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:35:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-167-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-167.ec2.internal
      uid: b11d8dcb-0eda-47bb-aeb4-080b493a977e
    resourceVersion: "29828"
    uid: 761e9404-3207-494f-88b2-f53f15695690
  spec:
    sourcePod: network-check-source-dbd9cf844-f2wfw
    targetEndpoint: ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:33:35Z"
      message: 'load-balancer-api-internal: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.095696ms
      message: 'load-balancer-api-internal: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 8.524396ms
      message: 'load-balancer-api-internal: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 4.818394ms
      message: 'load-balancer-api-internal: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 9.664122ms
      message: 'load-balancer-api-internal: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 6.325486ms
      message: 'load-balancer-api-internal: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 9.359463ms
      message: 'load-balancer-api-internal: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 5.93654ms
      message: 'load-balancer-api-internal: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 9.742056ms
      message: 'load-balancer-api-internal: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 6.6507ms
      message: 'load-balancer-api-internal: tcp connection to ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:35:35Z"
    - latency: 8.543412ms
      message: 'load-balancer-api-internal: resolved host name ac845ea63c32a4e91986d3f02c6971f3-6d172959c1884b5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:35:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-167-to-network-check-target-ip-10-0-128-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-167.ec2.internal
      uid: b11d8dcb-0eda-47bb-aeb4-080b493a977e
    resourceVersion: "31081"
    uid: 3535155e-58d8-4857-a8de-00a5bcb08244
  spec:
    sourcePod: network-check-source-dbd9cf844-f2wfw
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:34:35Z"
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.004µs
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:41:35Z"
    - latency: 1.320202ms
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:40:35Z"
    - latency: 1.140157ms
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 1.192731ms
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 895.941µs
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 913.604µs
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 834.483µs
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:35:35Z"
    - latency: 851.049µs
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:34:35Z"
    - latency: 835.675µs
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:33:35Z"
    - latency: 1.073733ms
      message: 'network-check-target-ip-10-0-128-167: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:32:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-167-to-network-check-target-ip-10-0-130-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-167.ec2.internal
      uid: b11d8dcb-0eda-47bb-aeb4-080b493a977e
    resourceVersion: "31083"
    uid: 42144c6e-abc6-4c3c-a115-70bfa5654eca
  spec:
    sourcePod: network-check-source-dbd9cf844-f2wfw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:34:35Z"
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.145971ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:41:35Z"
    - latency: 2.207571ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:40:35Z"
    - latency: 2.003905ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 2.101897ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 1.815078ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 2.117911ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 2.351198ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:35:35Z"
    - latency: 2.162995ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:34:35Z"
    - latency: 2.084598ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:33:35Z"
    - latency: 2.002761ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:32:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-167-to-network-check-target-ip-10-0-141-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-167.ec2.internal
      uid: b11d8dcb-0eda-47bb-aeb4-080b493a977e
    resourceVersion: "31082"
    uid: 90257ac0-866e-42d4-b812-92dc9bca7420
  spec:
    sourcePod: network-check-source-dbd9cf844-f2wfw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:34:35Z"
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.96549ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:41:35Z"
    - latency: 2.133375ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:40:35Z"
    - latency: 2.13424ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 2.284809ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 1.861061ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 2.186187ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 2.178066ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:35:35Z"
    - latency: 2.443565ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:34:35Z"
    - latency: 2.389672ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:33:35Z"
    - latency: 2.131232ms
      message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:32:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-167-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-167.ec2.internal
      uid: b11d8dcb-0eda-47bb-aeb4-080b493a977e
    resourceVersion: "29826"
    uid: 283d6b98-6dc4-49bd-8b08-2a8abc7404a8
  spec:
    sourcePod: network-check-source-dbd9cf844-f2wfw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:33:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.14695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 1.770411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:39:35Z"
    - latency: 1.162851ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 1.898052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:38:35Z"
    - latency: 908.021µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 1.681722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:37:35Z"
    - latency: 1.186753ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 2.035333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:36:35Z"
    - latency: 1.169712ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:35:35Z"
    - latency: 1.737759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T00:35:35Z"
kind: List
metadata:
  resourceVersion: ""