使用helm安装后graphd的pod和statefulset一直不出现。

提问参考模版:

  • nebula 版本:3.6.0

  • Operator 版本:1.8.0

  • 部署方式:分部署

  • 安装方式:Helm

  • 是否上生产环境:N

  • 问题的具体描述:
    执行helm install后一直没有graphd相关pod和statefulset出现,且storaged的状态一直是not ready

  • 日志信息
    metad:

storaged:


values.yaml:

nebula:
  version: v3.8.0
  imagePullPolicy: IfNotPresent
  storageClassName: openebs-hostpath
  enablePVReclaim: false
  enableBR: false
  enableForceUpdate: false
  schedulerName: default-scheduler # nebula-scheduler
  logRotate: {}
  reference:
    name: statefulsets.apps
    version: v1
  graphd:
    image: docker-proxy.xgate.com/vesoft/nebula-graphd
    replicas: 2
    serviceType: NodePort
    env: []
    config: {}
    resources:
      requests:
        cpu: "0"
        memory: "500Mi"
      limits:
        cpu: "1"
        memory: "500Mi"
    logVolume:
      enable: true
      storage: "500Mi"
    podLabels: {}
    podAnnotations: {}
    securityContext: {}
    nodeSelector: {}
    tolerations: []
    affinity: {}
    readinessProbe: {}
    livenessProbe: {}
    initContainers: []
    sidecarContainers: []
    volumes: []
    volumeMounts: []

  metad:
    image: docker-proxy.xgate.com/vesoft/nebula-metad
    replicas: 3
    env: []
    config: {}
    resources:
      requests:
        cpu: "0"
        memory: "500Mi"
      limits:
        cpu: "1"
        memory: "1Gi"
    logVolume:
      enable: true
      storage: "500Mi"
    dataVolume:
      storage: "2Gi"
    licenseManagerURL: ""
    license: {}
    podLabels: {}
    podAnnotations: {}
    securityContext: {}
    nodeSelector: {}
    tolerations: []
    affinity: {}
    readinessProbe: {}
    livenessProbe: {}
    initContainers: []
    sidecarContainers: []
    volumes: []
    volumeMounts: []

  storaged:
    image: docker-proxy.xgate.com/vesoft/nebula-storaged
    replicas: 3
    env: []
    config: {}
    resources:
      requests:
        cpu: "0"
        memory: "50Mi"
      limits:
        cpu: "1"
        memory: "1Gi"
    logVolume:
      enable: true
      storage: "500Mi"
    dataVolumes:
    - storage: "10Gi"
    enableAutoBalance: false
    podLabels: {}
    podAnnotations: {}
    securityContext: {}
    nodeSelector: {}
    tolerations: []
    affinity: {}
    readinessProbe: {}
    livenessProbe: {}
    initContainers: []
    sidecarContainers: []
    volumes: []
    volumeMounts: []

  exporter:
    image: docker-proxy.xgate.com/vesoft/nebula-stats-exporter
    version: v3.3.0
    replicas: 1
    env: []
    resources:
      requests:
        cpu: "0"
        memory: "128Mi"
      limits:
        cpu: "200m"
        memory: "256Mi"
    podLabels: {}
    podAnnotations: {}
    securityContext: {}
    nodeSelector: {}
    tolerations: []
    affinity: {}
    readinessProbe: {}
    livenessProbe: {}
    initContainers: []
    sidecarContainers: []
    volumes: []
    volumeMounts: []
    maxRequests: 20

  agent:
    image: docker-proxy.xgate.com/vesoft/nebula-agent
    version: latest
    resources:
      requests:
        cpu: "0"
        memory: "0"
      limits:
        cpu: "200m"
        memory: "256Mi"
    env: []
    volumeMounts: []

  console:
    username: root
    password: nebula
    image: docker-proxy.xgate.com/vesoft/nebula-console
    version: latest
    nodeSelector: {}

  alpineImage: docker-proxy.xgate.com/vesoft/nebula-alpine

  sslCerts: {}

imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""

补充下operator的日志:

然而storaged的ip为10.244.0.154,metad为153

原因找到了,容器中的/etc/resolv.conf内容如下:

将options ndots:5改为1后恢复正常

2 个赞

此话题已在最后回复的 30 天后被自动关闭。不再允许新回复。