Error: unknown flag: --name & -f values.yaml

[yoomnguyen]

Greeting,

I am following the Readme installation to deploy nextcloud on K8 but got an error.
Why --name & -f values.yaml won't work. That is what the instructions recommended.

Here is the install instruction link.
https://github.com/nextcloud/helm/tree/master/charts/nextcloud

Am I doing something wrong here or the instruction is incorrect?

1. first attempt with Error
   helm install --name my-nextcloud --namespace nextcloud -f values.yaml nextcloud/nextcloud

####GET THIS ERROR######
Error: unknown flag: --name

############
2. when I ran helm --help
helm doesn't have such option --name or -f

##########
3. HOW TO INCLUDE values.yaml ?

what is the right flag to use to include the values.yaml file?

Info: helm version
v3.11.1

[jessebot]

Can you try without the the --name and with --values instead, like:

 helm install my-nextcloud --namespace nextcloud --values values.yaml nextcloud/nextcloud

[yoom2016]

Thank you. I tried that and it ran without complain.

However, the manifest values.yaml did not included or take effect, meaning the defines parameters define in the values.yaml did not take effect. For example: I have changes the password, enable the external database postgres and set service:
type: LoadBalancer in the values.yaml

I don't see evidents that the values.yaml has been included.
There is not LoadBalancer IP
The default password still: changeme
and this error

#######################################################################################################

WARNING: You did not provide an external database host in your 'helm install' call

Running Nextcloud with the integrated sqlite database is not recommended for production instances

#######################################################################################################

Any suggestion?

[jessebot]

Could you please anonymize any sensitive data (change any passwords and also any personal domains or IP addresses) in your values.yaml and then post it here? That way I can take a look and make sure nothing is wrong.

Can you also tell me what distribution and version of kubernetes you are running? (example distros: GKE, KinD, k3s, etc) For k8s distros, we're only supporting what is currently in support, so 1.23,1.24,1.25, and future releases. This is just so that we can spin up the same kind of cluster as you though, and then I, or one of the other people in the nextcloud community can test if we get the same issue.

Thanks for all your patience on this. I know it can be really frustrating when a helm chart doesn't work; That's why I volunteer time to help others on this, but I can only do it on my off hours from my day job, so sometimes responses are slow. Others from the community can drop by though, so I always try to move forward an issue by at least collecting more data for the next person.

[yoom2016]

Ubuntu on bare metal, K8 v1.26.0

1. Deploy postgresql database session

helm install --namespace nextcloud nextcloud bitnami/postgresql
--set persistence.enabled=true
--set persistence.existingClaim=cephfs-nextcloud-postgresql-pvc \

2. Deploy Nexcloud session
   helm install my-nextcloud --namespace nextcloud --value values.yaml nextcloud/nextcloud

3. values.yaml contents

---

create namespace
apiVersion: v1
kind: Namespace
metadata:
name: nextcloud

image:
repository: nextcloud

tag: 24.0.3-apache

pullPolicy: IfNotPresent

pullSecrets:

- myRegistrKeySecretName

nameOverride: ""
fullnameOverride: ""
podAnnotations: {}
deploymentAnnotations: {}
deploymentLabels: {}

Number of replicas to be deployed

replicaCount: 2

Allowing use of ingress controllers

ref: https://kubernetes.io/docs/concepts/services-networking/ingress/

ingress:
enabled: true
className: nginx
annotations: {}
nginx.ingress.kubernetes.io/proxy-body-size: 4G
kubernetes.io/tls-acme: "true"
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/server-snippet: |-
server_tokens off;
proxy_hide_header X-Powered-By;

  rewrite ^/.well-known/webfinger /public.php?service=webfinger 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:
- mynextcloud.example.com
labels: {}
path: /
pathType: Prefix

Allow configuration of lifecycle hooks

ref: https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/

lifecycle: {}

postStartCommand: []

preStopCommand: []

phpClientHttpsFix:
enabled: false
protocol: https

nextcloud:
host: mynextcloud.example.com
username: admin
password: Spring2023

Use an existing secret

existingSecret:
enabled: false
# secretName: nameofsecret
# usernameKey: nextcloud-username
# passwordKey: nextcloud-password
# tokenKey: nextcloud-token
# smtpUsernameKey: smtp-username
# smtpPasswordKey: smtp-password
update: 0

If web server is not binding default port, you can define it

containerPort: 80
datadir: /var/www/html/data
persistence:
subPath:
mail:
enabled: true
fromAddress: nextcloud
domain: example.com
smtp:
host: mail.example.com
secure: ssl
port: 8443
authtype: LOGIN
name: nextcloud
password: Spring2023

PHP Configuration files

Will be injected in /usr/local/etc/php/conf.d for apache image and in /usr/local/etc/php-fpm.d when nginx.enabled: true

phpConfigs: {}

Default config files

IMPORTANT: Will be used only if you put extra configs, otherwise default will come from nextcloud itself

Default confgurations can be found here: https://github.com/nextcloud/docker/tree/master/16.0/apache/config

defaultConfigs:
# To protect /var/www/html/config
.htaccess: true
# Redis default configuration
redis.config.php: false
# Apache configuration for rewrite urls
apache-pretty-urls.config.php: true
# Define APCu as local cache
apcu.config.php: true
# Apps directory configs
apps.config.php: true
# Used for auto configure database
autoconfig.php: false
# SMTP default configuration
smtp.config.php: true

Extra config files created in /var/www/html/config/

ref: https://docs.nextcloud.com/server/15/admin_manual/configuration_server/config_sample_php_parameters.html#multiple-config-php-file

configs: {}

configs:
custom.config.php: |-
<?php
$CONFIG = array (
'overwriteprotocol' => 'https',
'overwrite.cli.url' => 'https://mynextcloud.example.com',
'filelocking.enabled' => 'true',
'loglevel' => '2',
'enable_previews' => true,
'trusted_domains' =>
[
'example.com',
'mynextcloud.example.com'
]
);

redis.config.php: |-
<?php
$CONFIG = array (
'memcache.local' => '\OC\Memcache\Redis',
'memcache.distributed' => '\OC\Memcache\Redis',
'memcache.locking' => '\OC\Memcache\Redis',
'redis' => array(
'host' => getenv('REDIS_HOST'),
'port' => getenv('REDIS_HOST_PORT') ?: 6379,
'password' => getenv('REDIS_HOST_PASSWORD')
)
);

Strategy used to replace old pods

IMPORTANT: use with care, it is suggested to leave as that for upgrade purposes

ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy

strategy:
type: Recreate
# type: RollingUpdate
# rollingUpdate:
# maxSurge: 1
# maxUnavailable: 0

Extra environment variables

extraEnv:

- name: SOME_SECRET_ENV

valueFrom:

secretKeyRef:

name: nextcloud

key: secret_key

Extra init containers that runs before pods start.

extraInitContainers: []

- name: do-something

image: busybox

command: ['do', 'something']

Extra sidecar containers.

extraSidecarContainers: []

- name: nextcloud-logger

image: busybox

command: [/bin/sh, -c, 'while ! test -f "/run/nextcloud/data/nextcloud.log"; do sleep 1; done; tail -n+1 -f /run/nextcloud/data/nextcloud.log']

volumeMounts:

- name: nextcloud-data

mountPath: /run/nextcloud/data

Extra mounts for the pods. Example shown is for connecting a legacy NFS volume

to NextCloud pods in Kubernetes. This can then be configured in External Storage

extraVolumes:

- name: nfs

nfs:

server: "10.0.0.1"

path: "/nextcloud_data"

readOnly: false

extraVolumeMounts:

- name: nfs

mountPath: "/legacy_data"

Set securityContext parameters. For example, you may need to define runAsNonRoot directive

securityContext: {}

runAsUser: "33"

runAsGroup: "33"

runAsNonRoot: true

readOnlyRootFilesystem: true

Set securityContext parameters for the pod. For example, you may need to define runAsNonRoot directive

podSecurityContext: {}

runAsUser: "33"

runAsGroup: "33"

runAsNonRoot: true

readOnlyRootFilesystem: true

nginx:

You need to set an fpm version of the image for nextcloud if you want to use nginx!

enabled: false
image:
repository: nginx
tag: alpine
pullPolicy: IfNotPresent

config:
# This generates the default nginx config as per the nextcloud documentation
default: true
# custom: |-
# worker_processes 1;..

resources: {}

Set securityContext parameters. For example, you may need to define runAsNonRoot directive

securityContext: {}

runAsUser: "82"

internalDatabase:
enabled: false
name: nextcloud

External database configuration

externalDatabase:
enabled: true

Supported database engines: mysql or postgresql

type: postgresql

Database host

host: postgresql-primary

Database user

user:

Database password

password:

Database name

database: nextcloud

Use a existing secret

existingSecret:
enabled: true
secretName: nextcloud-db-entry
usernameKey: nextcloud
passwordKey: Spring2023

MariaDB chart configuration

mariadb:

Whether to deploy a mariadb server to satisfy the applications database requirements. To use an external database set this to false and configure the externalDatabase parameters

enabled: false

auth:
database: nextcloud
username: nextcloud
password: Spring

architecture: standalone

configuraton and other stuff store here, share with the Postgresql PVC. user data store on a different PVC

primary:
persistence:
enabled: true
# existingClaim: "cephfs-nextcloud-postgresql-pvc"
# storageClass: "rook-cephfs"
accessMode: ReadWriteMany
size: 15Gi

PostgreSQL chart configuration

for more options see https://github.com/bitnami/charts/tree/master/bitnami/postgresql

postgresql:
enabled: true
global:
postgresql:
auth:
username: nextcloud
password: Spring2023
database: nextcloud
primary:
persistence:
enabled: true
existingClaim: "cephfs-nextcloud-postgresql-pvc"
storageClass: "rook-cephfs"

Redis chart configuration

for more options see https://github.com/bitnami/charts/tree/master/bitnami/redis

redis:
enabled: true
auth:
enabled: true
password: 'Spring2023'

Cronjob to execute Nextcloud background tasks

ref: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html#cron

cronjob:
enabled: true
annotations: {}
curlInsecure: false
failedJobsHistoryLimit: 5
image: {}
schedule: '*/5 * * * *'
successfulJobsHistoryLimit: 2

Cronjob sidecar resource requests and limits

ref: http://kubernetes.io/docs/user-guide/compute-resources/

resources: {}

Allow configuration of lifecycle hooks

ref: https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/

lifecycle: {}
# postStartCommand: []
# preStopCommand: []

Set securityContext parameters. For example, you may need to define runAsNonRoot directive

securityContext: {}

runAsUser: "33"

runAsGroup: "33"

runAsNonRoot: true

readOnlyRootFilesystem: true

service:
type: LoadBalancer
port: 80
loadBalancerIP: 192.168.0.203
nodePort: 80

Enable persistence using Persistent Volume Claims

ref: http://kubernetes.io/docs/user-guide/persistent-volumes/

persistence:

Nextcloud Data (/var/www/html)

enabled: true
annotations:

nextcloud data Persistent Volume Storage Class

If defined, storageClassName:

If set to "-", storageClassName: "", which disables dynamic provisioning

If undefined (the default) or set to null, no storageClassName spec is

set, choosing the default provisioner. (gp2 on AWS, standard on

GKE, AWS & OpenStack)

storageClass: "rook-cephfs"

A manually managed Persistent Volume and Claim

Requires persistence.enabled: true

If defined, PVC must be created manually before volume will be bound

existingClaim: "cephfs-nextcloud-data-pvc"

accessMode: ReadWriteOnce

accessMode: ReadWriteMany
size: 1Ti

Use an additional pvc for the data directory rather than a subpath of the default PVC

Useful to store data on a different storageClass (e.g. on slower disks)

Use an additional pvc for the data directory rather than a subpath of the default PVC

Useful to store data on a different storageClass (e.g. on slower disks)

nextcloudData:
enabled: true
subPath:
annotations:
storageClass: "rook-cephfs"
existingClaim: "cephfs-nextcloud-data-pvc"
accessMode: ReadWriteMany
size: 1Ti

resources: {}

We usually recommend not to specify default resources and to leave this as a conscious

choice for the user. This also increases chances charts run on environments with little

resources, such as Minikube. If you do want to specify resources, uncomment the following

lines, adjust them as necessary, and remove the curly braces after 'resources:'.

limits:

cpu: 100m

memory: 128Mi

requests:

cpu: 100m

memory: 128Mi

Liveness and readiness probe values

Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes

livenessProbe:
enabled: true
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 3
successThreshold: 1
readinessProbe:
enabled: true
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 3
successThreshold: 1
startupProbe:
enabled: false
initialDelaySeconds: 30
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 30
successThreshold: 1

Enable pod autoscaling using HorizontalPodAutoscaler

ref: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/

hpa:
enabled: true
cputhreshold: 60
minPods: 1
maxPods: 10

nodeSelector: {}

tolerations: []

affinity: {}

Prometheus Exporter / Metrics

metrics:
enabled: true

replicaCount: 1

The metrics exporter needs to know how you serve Nextcloud either http or https

https: false

Use API token if set, otherwise fall back to password authentication

https://github.com/xperimental/nextcloud-exporter#token-authentication

Currently you still need to set the token manually in your nextcloud install

token: ""
timeout: 5s

if set to true, exporter skips certificate verification of Nextcloud server.

tlsSkipVerify: false

image:
repository: xperimental/nextcloud-exporter
tag: 0.6.0
pullPolicy: IfNotPresent

Metrics exporter pod Annotation and Labels

podAnnotations: {}

podLabels: {}

service:
type: ClusterIP
## Use serviceLoadBalancerIP to request a specific static IP,
## otherwise leave blank
# loadBalancerIP:
annotations:
prometheus.io/scrape: "true"
prometheus.io/port: "9205"
labels: {}

Prometheus Operator ServiceMonitor configuration

serviceMonitor:
## @param metrics.serviceMonitor.enabled Create ServiceMonitor Resource for scraping metrics using PrometheusOperator
##
enabled: false

## @param metrics.serviceMonitor.namespace Namespace in which Prometheus is running
##
namespace: ""

## @param metrics.serviceMonitor.jobLabel The name of the label on the target service to use as the job name in prometheus.
##
jobLabel: ""

## @param metrics.serviceMonitor.interval Interval at which metrics should be scraped
## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#endpoint
##
interval: 30s

## @param metrics.serviceMonitor.scrapeTimeout Specify the timeout after which the scrape is ended
## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#endpoint
##
scrapeTimeout: ""

## @param metrics.serviceMonitor.labels Extra labels for the ServiceMonitor
##
labels: {}

rbac:
enabled: false
serviceaccount:
create: true
name: nextcloud-serviceaccount
annotations: {}

@param securityContext @deprecated Use nextcloud.podSecurityContext instead

securityContext: {}

[jessebot]

Could you please modify your answer to use a syntax highlighted codeblock. You can follow the instructions here. As an example here's what you could do for just a small block:

which would produce this:

If you can wrap all of your values.yaml in like I've shown above, then it will be much easier to read. :) Sorry for the inconvenience.