使用Bitnami Helm图表无缘无故地停止密钥披风

Question

我正在尝试部署一个带有postgres数据库的keycloak服务器，使用bitnami舵图配置如下所示的通量。

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: keycloak-release
  namespace: keycloak
spec:
  releaseName: keycloak
  targetNamespace: keycloak
  chart:
    spec:
      chart: keycloak
      version: 7.1.x
      sourceRef:
        kind: HelmRepository
        name: bitnami-repo
        namespace: flux-system
  interval: '10s'
  install:
    remediation:
      retries: 3
    timeout: '10m0s'
  values:
    image:
      debug: true
    containerPorts:
      http: 8080
      https: 8443
      management: 9990
    resources:
      limits:
        memory: 256Mi
        cpu: 250m
      requests:
        memory: 256Mi
        cpu: 250m
    service:
      type: NodePort
      ports:
        postgresql: 5432
    postgresql:
      enabled: true
      auth:
        existingSecret: postgres-keycloak
    auth:
      existingSecret: keycloak-secret
    livenessProbe:
      enabled: true
      httpGet:
        path: /auth/
        port: http
      initialDelaySeconds: 300
      periodSeconds: 1
      timeoutSeconds: 5
      failureThreshold: 3
      successThreshold: 1
    readinessProbe:
      enabled: true
      httpGet:
        path: /auth/realms/master
        port: http
      initialDelaySeconds: 30
      periodSeconds: 10
      timeoutSeconds: 1
      failureThreshold: 3
      successThreshold: 1
    extraEnvVars:
      - name: KEYCLOAK_ALWAYS_HTTPS
        value: "true"
      - name: PROXY_ADDRESS_FORWARDING
        value: "true"
      - name: JAVA_OPTS_APPEND
        value: "-Djboss.as.management.blocking.timeout=7200"
      - name : KEYCLOAK_HTTP_PORT
        value : "8080"
      - name: KEYCLOAK_HTTPS_PORT
        value: "8443"
    extraVolumes:
      - name: disable-theme-cache-volume
        configMap:
          name: disable-theme-cache
    extraVolumeMounts:
      - name: disable-theme-cache-volume
        mountPath: /opt/jboss/startup-scripts

但是，似乎存在一个joss问题，因为容器从未启动，服务器在没有任何特定原因的情况下停止。

​

​

我认为问题肯定在某些jboss配置中，但我看不出是什么原因。有什么想法吗？)

Answer 1

我的第一个猜测是，资源限制可能太过限制。至少记忆应该更多。

resources:
      limits:
        memory: 256Mi
        cpu: 250m
      requests:
        memory: 256Mi
        cpu: 250m