Karl DeBisschop

@JordyBottelier You ask if I have tested -- yes, I am using it now. Thanks for the feedback on commenting -- I will see if I can clarify.

@ltamaster i don't see how the random orchestrator solves my concern. It allows me to apply to the same number of pods as I have deployments. But, as far as...

I'm facing a similar problem... Because the pod resource model can have multiple pods per deployment, if I try to run an script across all my deployments, it actually runs...

You're right -- my comment was a bit unclear. A minor difference is that I want to run a command rather than a script. The main difference is that I...

I have just created a pull request (https://github.com/rundeck-plugins/kubernetes/pull/131) to illustrate the approach I have taken...it may not be as aesthetically correct as defining a node resource based on the ReplicaSet...

The OP was using kubernetes==12.0.1 but the plugin requires 11.0.0

@palnabarun it looks you self-assigned this. It seems like a tough nut to crack. Have you made any progress? Is there anything I can do to help?

As a way to handle this on Ubuntu without altering the distributed files, I used the reference to /etc/sysconfig/wazuh-indexer in the systemd file: ``` sudo mkdir -p /var/lib/wazuh-indexer/tmp sudo chmod...

I would love to bubble this back up. It is critical functionality for us and I have confirmed that the random selector in general runs the same command in some...

It turns out that this is sort of unnecessary. You can actually just specify additional options in the list of sources ... they will just get passed along through that...