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 tried to use the worker hpa but it fails because of an undefined template: netbox/templates/worker-hpa.yaml:7:8: executing \"netbox/templates/worker-hpa.yaml\" at <include \"netbox.worker.labels\" .>: error calling include: template: no template \"netbox.worker.labels\" associated with template \"gotpl\"\n"
I'm not that familiar with helm but from my perspective the fix might just be changing the netbox.worker.labels to netbox.labels in worker-hpa.yaml?
kind regards,
Jan
The text was updated successfully, but these errors were encountered:
This is easy enough to fix, but come to think of it is there a valid use case for running more than one worker instance? Would it be more correct to remove the HPA and restrict the worker Deployment to only 1 replica?
We are currently using 4 workers for our deployment. With a lot of data in netbox and maybe (like in our case) some plugins that do use the workers as well it makes perfect sense to have more than one, especially if you have some longer running tasks that block a single worker.
Hi,
I tried to use the worker hpa but it fails because of an undefined template:
netbox/templates/worker-hpa.yaml:7:8: executing \"netbox/templates/worker-hpa.yaml\" at <include \"netbox.worker.labels\" .>: error calling include: template: no template \"netbox.worker.labels\" associated with template \"gotpl\"\n"
I'm not that familiar with helm but from my perspective the fix might just be changing the netbox.worker.labels to netbox.labels in worker-hpa.yaml?
kind regards,
Jan
The text was updated successfully, but these errors were encountered: