Stephan
@jessebot I'm using the helm chart version `3.1.2`, see below my `values.yaml` file: ```yaml ingress: enabled: true annotations: kubernetes.io/ingress.class: nginx cert-manager.io/cluster-issuer: duckdns-webhook-cert-manager-webhook-duckdns-${environment} nginx.ingress.kubernetes.io/proxy-body-size: 32M nginx.ingress.kubernetes.io/server-snippet: |- location = /.well-known/carddav {...
@jessebot: - `${nextcloud_domain}` is the FQDN `*.duckdns.org` - `${ip_address}` is the `172.16.x.y` address I'm also using metallb.
Hi, bitnami doesn't support arm64. I had the same problem with postgresql, you just can use the official redis image. Just put the following code into your values.yaml file: ```yaml...
Sorry, for that. But what looks strange to me is the path in the logs: `/opt/bitnami/scripts/start-scripts/start-master.sh` The `bitnami` folder is a bit strange there I think.
I have a similar problem: https://github.com/nextcloud/helm/issues/114
I'm running into a similar problem. I want to use "Tenant VRF" on a tenant but when I activate it, deploy the operator and setup an demo applicaiton I'm getting...
Hi, we are running into the same problem. Thx to @akinsella-socrate for the fix but as mentioned in the [PR](https://github.com/zitadel/terraform-provider-zitadel/pull/153#issuecomment-1993733234) it is closed because the merge of main into your...
Hi, we are running into the same issue. Any updates on this topic?
> can you add your use case here : [goharbor/harbor#20076](https://github.com/goharbor/harbor/issues/20076) ? done