You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using ArgoCD instead of Flux, typically a simple conversion with Helm. The app-template chart is not as well documented yet, so I might have missed something specifically with configMaps.
Getting an error the config file is mounted as a directory:
Traceback (most recent call last):
File "/usr/local/go2rtc/create_config.py", line 18, in <module>
with open(config_file) as f:
IsADirectoryError: [Errno 21] Is a directory: '/config/config.yml'
I couldn't find an example of app-template chart using a configMaps section within the values section of the Helm Release. I could only find external configMap being referenced. Wondering if this is a known issue? broken? It was pretty straight forward using it with k8s-at-home charts. The docs don't have a reference example yet.
The text was updated successfully, but these errors were encountered:
Modeling Frigate Deployment based on:
https://github.com/onedr0p/home-ops/blob/main/kubernetes/apps/default/frigate/app/helmrelease.yaml
I'm using ArgoCD instead of Flux, typically a simple conversion with Helm. The
app-template
chart is not as well documented yet, so I might have missed something specifically with configMaps.Getting an error the config file is mounted as a directory:
My
values.yaml
section has this:ArgoCD does add the prefix "frigate-", so the above name accounts for that.
And I have a
configMaps
section for theconfigmap
.Reviewing the resulting StatefulSet deployment, it has:
Seems to be generated ok:
I couldn't find an example of
app-template
chart using aconfigMaps
section within thevalues
section of the Helm Release. I could only find external configMap being referenced. Wondering if this is a known issue? broken? It was pretty straight forward using it withk8s-at-home
charts. The docs don't have a reference example yet.The text was updated successfully, but these errors were encountered: