7.2. 如何使用 MicroShift 健康检查命令


microshift healthcheck 命令检查提供类型的工作负载是否存在,并验证指定超时持续时间的状态。就绪副本数(即 pod)必须与预期数量匹配。

要成功运行 microshift healthcheck 命令,请使用以下先决条件:

  • 从 root 用户帐户执行命令。
  • 启用 MicroShift 服务。

您可以在 microshift healthcheck 命令中添加以下操作:

  • -v=2 来提高输出的详细程度
  • --timeout="${WAIT_TIMEOUT_SECS}s",以覆盖默认的 600s 超时值
  • --namespace '< namespace> 指定工作负载的命名空间
  • --deployments '<application-deployment > 以检查特定部署的就绪情况

    示例命令

    $ sudo microshift healthcheck -v=2 --timeout="300s" --namespace busybox --deployments busybox-deployment
    Copy to Clipboard Toggle word wrap

    输出示例

    ??? I0410 08:54:03.766578    5898 service.go:29] microshift.service is enabled
    ??? I0410 08:54:03.766699    5898 service.go:31] Waiting 5m0s for microshift.service to be ready
    ??? I0410 08:54:03.768794    5898 service.go:38] microshift.service is ready
    ??? I0410 08:54:03.770585    5898 utils.go:34] Waiting for 1 goroutines
    ??? I0410 08:54:03.770955    5898 workloads.go:94] Waiting 5m0s for deployment/busybox-deployment in busybox
    ??? I0410 08:54:03.777830    5898 workloads.go:132] Deployment/busybox-deployment in busybox is ready
    ??? I0410 08:54:03.777858    5898 healthcheck.go:75] Workloads are ready
    Copy to Clipboard Toggle word wrap

microshift healthcheck 命令还接受以下附加参数来指定其他类型的工作负载:

  • --daemonsets
  • --statefulsets
  • 这些选项采用以逗号分隔的资源列表,例如:- daemonsets ovnkube-master,ovnkube-node

另外,a- custom 选项可与 JSON 字符串一起使用,例如:

$ sudo microshift healthcheck --custom '{"openshift-storage":{"deployments":
    ["lvms-operator"], "daemonsets": ["vg-manager"]}, "openshift-ovn-kubernetes":
    {"daemonsets": ["ovnkube-master", "ovnkube-node"]}}'
Copy to Clipboard Toggle word wrap

输出示例

??? I0410 08:54:25.291059    5979 service.go:29] microshift.service is enabled
??? I0410 08:54:25.291167    5979 service.go:31] Waiting 5m0s for microshift.service to be ready
??? I0410 08:54:25.293188    5979 service.go:38] microshift.service is ready
??? I0410 08:54:25.294331    5979 workloads.go:58] Waiting 5m0s for daemonset/ovnkube-node in openshift-ovn-kubernetes
??? I0410 08:54:25.294351    5979 workloads.go:58] Waiting 5m0s for daemonset/ovnkube-master in openshift-ovn-kubernetes
??? I0410 08:54:25.294331    5979 workloads.go:58] Waiting 5m0s for daemonset/vg-manager in openshift-storage
??? I0410 08:54:25.294341    5979 workloads.go:94] Waiting 5m0s for deployment/lvms-operator in openshift-storage
??? I0410 08:54:25.309739    5979 workloads.go:89] Daemonset/ovnkube-node in openshift-ovn-kubernetes is ready
??? I0410 08:54:25.310213    5979 workloads.go:89] Daemonset/vg-manager in openshift-storage is ready
??? I0410 08:54:25.310731    5979 workloads.go:132] Deployment/lvms-operator in openshift-storage is ready
??? I0410 08:54:25.311017    5979 workloads.go:89] Daemonset/ovnkube-master in openshift-ovn-kubernetes is ready
??? I0410 08:54:25.311189    5979 healthcheck.go:52] Workloads are ready
Copy to Clipboard Toggle word wrap

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat