Changing nextcloud.host vars results in crashloopbackoff
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- helm, kubernetes, yaml
- 领域
- devops, infrastructure
调研方向
从提供的 values.yaml 开始,在 Helm chart version 5.5.2 上复现该更改,并比较更改 nextcloud.host 前后渲染出的配置和 Nextcloud 容器的启动行为。检查 chart 中与 host 相关的模板以及 deployment 日志;当更改主机名不再导致 CrashLoopBackOff 时,该 issue 即完成。
由索引模型根据 Issue 内容生成。
描述
Describe your Issue
Changing the helm value responsible for the ingress hostname and the nextcloud internal host results in crashloopbackoff.
After changing back the nextcloud.host to the old value the deployment come back online. But this help in this case because I and I'm sure many other needs to change the hostname sometimes because of a migration to a other network etc.
Changing
nextcloud:
host: mycoolserver.example.com
to
nextcloud:
host: mycoolserver.newnetwork.com
I need to change this because I want to use my other ingress controller which can be accessed from the WAN.
Logs and Errors
crashloopbackoff in the nexcloud container inside the nextcloud pod. Nothing helpfull inside the log. The log shows no indicator about this issue. It looks simply like a exit code 1
Describe your Environment
-
Kubernetes distribution: v1.30.2+rke2r1
-
Helm Version: ArgoCD version 2.11.7
-
Helm Chart Version: 5.5.2
-
values.yaml:
---
{{- if .Values.spec.nextcloud.enabled }}
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: nextcloud
namespace: {{ .Values.spec.argocdNamespace }}
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
destination:
namespace: nextcloud
server: 'https://kubernetes.default.svc'
project: default
source:
chart: nextcloud
path: '.'
repoURL: {{ .Values.spec.nextcloud.repoURL }}
targetRevision: {{ .Values.spec.nextcloud.targetRevision }}
helm:
values: |
nextcloud:
host: {{ .Values.spec.nextcloud.host }}
username: admin
password: {{ .Values.spec.nextcloud.nextcloudAdminPW }}
containerPort: 80
datadir: /var/www/html/data
configs:
custom-overwrite.config.php: |-
<?php
$CONFIG = array (
'overwrite.cli.url' => 'https://nextcloud.nextcloud.svc.cluster.local',
'overwriteprotocol' => 'https',
);
proxy.config.php: |-
<?php
$CONFIG = array (
'trusted_proxies' => array(
0 => '127.0.0.1',
1 => '10.0.0.0/8',
),
'forwarded_for_headers' => array('HTTP_X_FORWARDED_FOR'),
);
cronjob:
enabled: true
persistence:
enabled: true
size: 150Gi
storageClass: "{{ .Values.spec.nextcloud.storageClass }}"
image:
flavor: fpm
nginx:
enabled: true
externalDatabase:
enabled: true
type: mysql
host: nextcloud-mariadb.svc
user: nextcloud
password: "{{ .Values.spec.nextcloud.mariadbPW }}"
database: nextcloud
internalDatabase:
enabled: false
mariadb:
enabled: true
primary:
persistence:
enabled: true
storageClass: "{{ .Values.spec.nextcloud.storageClass }}"
auth:
database: nextcloud
username: nextcloud
password: "{{ .Values.spec.nextcloud.mariadbPW }}"
existingSecret: ""
ingress:
enabled: true
labels: {}
path: /
pathType: Prefix
className: nginx
annotations:
# cert-manager.io/cluster-issuer: letsencrypt-prod
cert-manager.io/cluster-issuer: selfsigned-issuer
nginx.ingress.kubernetes.io/enable-cors: "true"
nginx.ingress.kubernetes.io/cors-allow-headers: "X-Forwarded-For"
nginx.ingress.kubernetes.io/server-snippet: |-
server_tokens off;
proxy_hide_header X-Powered-By;
rewrite ^/.well-known/webfinger /index.php/.well-known/webfinger last;
rewrite ^/.well-known/nodeinfo /index.php/.well-known/nodeinfo last;
rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json;
location = /.well-known/carddav {
return 301 $scheme://$host/remote.php/dav;
}
location = /.well-known/caldav {
return 301 $scheme://$host/remote.php/dav;
}
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)/ {
deny all;
}
location ~ ^/(?:autotest|occ|issue|indie|db_|console) {
deny all;
}
tls:
- secretName: nextcloud-tls
hosts:
- {{ .Values.spec.nextcloud.host }}
syncPolicy:
automated:
selfHeal: true
allowEmpty: true
syncOptions:
- CreateNamespace=true
{{- end }}
- 主要语言
- Go Template
- 星标
- 536
- 派生
- 316
- 平均合并
- 4 天 16 小时
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nextcloud/helm 的其他 Issue
-
No native support for REDIS_USER enviroment var可能已有人在做 @jholmes802 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
nextcloud.openmetrics.allowedClients is silently ignored unless nextcloud.configs is set可能已有人在做 @JanWelker 于 17 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 78/100
-
External Redis not working: redis-session.ini: Permission denied可能已有人在做 @antoinetran 于 22 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 55/100
相似的 Issue
-
lens:agent lens:process process
难度 2/5 1-3 小时 新手友好度 78/100
thebristolsound/birdbrain#1771 ·
维护者通常 1 天内回复
-
ci-install-db-tools stall-case tests flake: stalled apt-get can be killed before it logs its call未关闭effort:low model:light plan planner:opus-5-5 tests
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
component/test-automation work/tech-debt
难度 2/5 1-3 小时 新手友好度 78/100
bcgov/bc-wallet-mobile#4845 ·
维护者通常 1 天内回复
-
first
难度 2/5 1-3 小时 新手友好度 72/100
AcademySoftwareFoundation/rmtc#54 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
stac-utils/stac-fastapi-elasticsearch-opensearch#932 ·
维护者通常 1 天内回复