- Published on
Running Gitea act-runner with https using helm with modified config file
- Authors

- Name
- Peter Peerdeman
- @peterpeerdeman
As I was upgrading my gitea setup to use https certificates, I noticed my act runner stopped working. Of course the url of the gitea instance had to be updated to include the 's' in https, but because I'm using self signed certificates, I needed to configure the act runner to allow these type of certificates.
I then realised that the act_runner-helm chart I was using doesn't supply an option to overwrite the default config file. As I found out, using a config map is the right way to supply your own version of a config file, so I created a fork that allows you to (for instance) set the insecure:true value false in the config.yaml file
apiVersion: v1
kind: ConfigMap
metadata:
name: act-runner-config
data:
config.yaml: |
runner:
insecure: true
labels: [
"ubuntu-latest:docker://node:16-bullseye"
]