You need to enable JavaScript to run this app. Docker Desktop用Helm部署3副本Vault其余Pod处于Pending状态排查
优惠活动
大模型
产品
解决方案
定价
更多

Docker Desktop用Helm部署3副本Vault其余Pod处于Pending状态排查

HashiCorp Vault 三副本部署部分Pod处于Pending状态

采用3副本模式部署HashiCorp Vault,Pod vault-0 处于Running状态,但其余两个Pod处于Pending状态。
初始部署状态截图

以下是自定义覆盖YAML配置:

# Vault Helm Chart Value Overrides
global:
  enabled: true
  tlsDisable: true

injector:
  enabled: true
  # Use the Vault K8s Image https://github.com/hashicorp/vault-k8s/
  image:
    repository: "hashicorp/vault-k8s"
    tag: "0.9.0"

  resources:
    requests:
      memory: 256Mi
      cpu: 250m
    limits:
      memory: 256Mi
      cpu: 250m
  affinity: ""
server:
  auditStorage:
    enabled: true
  standalone:
    enabled: false
  image:
    repository: "hashicorp/vault"
    tag: "1.6.3"
  resources:
    requests:
      memory: 4Gi
      cpu: 1000m
    limits:
      memory: 8Gi
      cpu: 1000m 
  ha:
    enabled: true
    replicas: 3    
    raft:
      enabled: true
      setNodeId: true
      config: |
        ui = true

        listener "tcp" {
          tls_disable = true
          address = "[::]:8200"
          cluster_address = "[::]:8201"
        }

        storage "raft" {
          path = "/vault/data"
        }

        service_registration "kubernetes" {}
    config: |
      ui = true

      listener "tcp" {
        tls_disable = true
        address = "[::]:8200"
        cluster_address = "[::]:8201"
      }

      service_registration "kubernetes" {}


# Vault UI
ui:
  enabled: true
  serviceType: "ClusterIP"
  externalPort: 8200

对处于Pending状态的Pod执行kubectl describe命令,查看返回的状态信息后,无法确认在覆盖配置文件中设置的亲和性参数是否正确,也不清楚问题出在哪里。当前通过Vault Helm Chart将服务部署到Docker Desktop本地集群,寻求相关问题解决帮助。
Pending Pod状态排查截图


内容的提问来源于stack exchange,提问作者Joshua

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.10.28 15:45:04