Hook artifacts not available for multi node clusters #42
Comments
ClashTheBunny
added a commit
to ClashTheBunny/tinkerbell-charts
that referenced
this issue
Aug 27, 2023
3 tasks
ClashTheBunny
added a commit
to ClashTheBunny/tinkerbell-charts
that referenced
this issue
Aug 27, 2023
fixes tinkerbell#42 for me Signed-off-by: Randall Mason <Randall@Mason.CH>
ClashTheBunny
added a commit
to ClashTheBunny/tinkerbell-charts
that referenced
this issue
Aug 27, 2023
fixes tinkerbell#42 for me Signed-off-by: Randall Mason <Randall@Mason.CH>
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the Hook artifacts are downloaded to a
hostPath. This is fine for single node Kubernetes clusters, but not for clusters with more than one.charts/tinkerbell/stack/templates/nginx.yaml
Line 88 in 2a4408f
Expected Behaviour
The stack chart should handle making the Hooks artifacts available for multiple nodes. Maybe a pluggable CSI option? Maybe, https://github.com/openebs/openebs or https://github.com/longhorn/longhorn
Current Behaviour
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
Operating System and version (e.g. Linux, Windows, MacOS):
How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:
Link to your project or a code example to reproduce issue:
The text was updated successfully, but these errors were encountered: