Describe the bug
- chart missing config/deployment for tor-controller-manager
To Reproduce
- deployment calls
/manager and can't find the binary ...
6m20s Warning Failed pod/tor-controller-569c85ccd4-vj5td Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/manager": stat /manager: no such file or directory: unknown
- can edit the deployment to point to
/app/manager and it works, but then it errors out because it cannot find controller_manager_config.yaml
Expected behavior
There are some resources deployed in hack/install.yaml that maybe required and not covered in the chart.
Deploying via the hack/install.yaml manifest throws errors that one of the resources is too large.
Additional information
tested in k3s under amd64 & arm64
System (please complete the following information):
- Platform: amd64, arm64
- Versions: k3s (arm64) 1.24.15 & k3s (amd64) 1.25.11
- Single-Node clusters, amd64 is Rocky Linux VM, arm64 is rpi4 with Ubuntu 20.04
Additional context
I had the previous chart (0.1.11) running on the rpi4 (arm64) for quite a while.
Describe the bug
To Reproduce
/managerand can't find the binary .../app/managerand it works, but then it errors out because it cannot findcontroller_manager_config.yamlExpected behavior
There are some resources deployed in
hack/install.yamlthat maybe required and not covered in the chart.Deploying via the
hack/install.yamlmanifest throws errors that one of the resources is too large.Additional information
tested in k3s under amd64 & arm64
System (please complete the following information):
Additional context
I had the previous chart (0.1.11) running on the rpi4 (arm64) for quite a while.