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
Is there any reason why loki-canary helm chart supports only daemonset?
We have many Loki nodes and on each runs loki canary (which is limited by node-selector). Would be great to have better control over how many canary instances are running.
We were considering deploying it independently with Deployment, but then when disabling canary from main loki helm chart we have to:
disable also helm tests
update canary image separately from main Loki helm chart
there is a risk that some incompatibility will arise in a long term when these two are separated
All we could wish for is to set deployment type to 'Deployment' and specify number of replicas.
Pros:
less pods and resources in our cluster
The text was updated successfully, but these errors were encountered:
Is there any reason why loki-canary helm chart supports only daemonset?
We have many Loki nodes and on each runs loki canary (which is limited by node-selector). Would be great to have better control over how many canary instances are running.
We were considering deploying it independently with Deployment, but then when disabling canary from main loki helm chart we have to:
All we could wish for is to set deployment type to 'Deployment' and specify number of replicas.
Pros:
The text was updated successfully, but these errors were encountered: