Skip to content
This repository has been archived by the owner on Nov 14, 2022. It is now read-only.

chore(deps): update helm release nextcloud to v3.3.3 #948

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 25, 2022

Mend Renovate

This PR contains the following updates:

Package Update Change
nextcloud (source) minor 3.1.2 -> 3.3.3

Release Notes

nextcloud/helm

v3.3.3

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

v3.3.2

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

v3.3.1

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

v3.3.0

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

v3.2.3

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

v3.2.2

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

v3.2.1

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.

v3.2.0

Compare Source

A file sharing server that puts the control and security of your own data back into your hands.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@github-actions
Copy link

github-actions bot commented Oct 25, 2022

Path: cluster/apps/selfhosted/nextcloud/helm-release.yaml
Version: 3.1.2 -> 3.3.3

@@ -169,6 +169,15 @@
   #    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:
@@ -289,47 +298,16 @@
     password: 'changeme'
 
 ## Cronjob to execute Nextcloud background tasks
-## ref: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html#webcron
+## ref: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html#cron
 ##
 cronjob:
   enabled: false
-  # Nexcloud image is used as default but only curl is needed
-  image: {}
-    # repository: nextcloud
-    # tag: 16.0.3-apache
-    # pullPolicy: IfNotPresent
-    # pullSecrets:
-    #   - myRegistrKeySecretName
-  # Every 5 minutes
-  # Note: Setting this to any any other value than 5 minutes might
-  #  cause issues with how nextcloud background jobs are executed
-  schedule: "*/5 * * * *"
-  annotations: {}
-  # Set curl's insecure option if you use e.g. self-signed certificates
-  curlInsecure: false
-  failedJobsHistoryLimit: 5
-  successfulJobsHistoryLimit: 2
-  # If not set, nextcloud deployment one will be set
-  # 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
-
-  # If not set, nextcloud deployment one will be set
-  # nodeSelector: {}
-
-  # If not set, nextcloud deployment one will be set
-  # tolerations: []
 
-  # If not set, nextcloud deployment one will be set
-  # affinity: {}
+  # Allow configuration of lifecycle hooks
+  # ref: https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/
+  lifecycle: {}
+    # postStartCommand: []
+    # preStopCommand: []
 
 service:
   type: ClusterIP
@@ -469,7 +447,7 @@
   ##
   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

@renovate renovate bot changed the title chore(deps): update helm release nextcloud to v3.2.0 chore(deps): update helm release nextcloud to v3.2.2 Nov 2, 2022
@renovate renovate bot force-pushed the renovate/nextcloud-3.x branch from 6f92708 to d503f4b Compare November 2, 2022 21:58
@renovate renovate bot changed the title chore(deps): update helm release nextcloud to v3.2.2 chore(deps): update helm release nextcloud to v3.2.3 Nov 3, 2022
@renovate renovate bot force-pushed the renovate/nextcloud-3.x branch 2 times, most recently from 4574532 to 3a2a969 Compare November 7, 2022 16:35
@renovate renovate bot changed the title chore(deps): update helm release nextcloud to v3.2.3 chore(deps): update helm release nextcloud to v3.3.0 Nov 7, 2022
@renovate renovate bot force-pushed the renovate/nextcloud-3.x branch from 3a2a969 to 4203cf6 Compare November 8, 2022 00:25
@renovate renovate bot changed the title chore(deps): update helm release nextcloud to v3.3.0 chore(deps): update helm release nextcloud to v3.3.2 Nov 8, 2022
@renovate renovate bot changed the title chore(deps): update helm release nextcloud to v3.3.2 chore(deps): update helm release nextcloud to v3.3.3 Nov 8, 2022
@renovate renovate bot force-pushed the renovate/nextcloud-3.x branch from 4203cf6 to d918875 Compare November 8, 2022 19:25
@Pumba98 Pumba98 closed this Nov 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant