Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Pod Support #3

Open
bobhenkel opened this issue Nov 28, 2017 · 3 comments
Open

Add Pod Support #3

bobhenkel opened this issue Nov 28, 2017 · 3 comments

Comments

@bobhenkel
Copy link

It would be very useful to use a pod as a node rather than the actual node.

@bobhenkel
Copy link
Author

Looks like skilld-labs/rundeck-kubernetes-step-plugin may do what I was asking for.

@jbguerraz jbguerraz reopened this Nov 29, 2017
@jbguerraz
Copy link
Member

Actually this is a good idea IMHO. We could get PODs from K8S and list them as Nodes in Rundeck. Then yet another plugin would allow to run commands over those nodes using K8S exec. That would be cool. For now we (Skilld) don't need it so we're not going to invest time in that yet but if one want to tackle it, that would be super!

@bobhenkel
Copy link
Author

bobhenkel commented Dec 7, 2017

Psuedo Idea:

  1. Rundeck needs to be able to target/list pods as it target/list nodes. Assuming these pods have a label that says I'm a rundeck-node... So kubectl get pods --selector=rundeck-node=true
  2. With the data of what pods we can run things on we can have rundeck run commands like it does on nodes, but on the pods. With something like kubectl exec one-of-the-labeled-pods-1668135175-3rn1l -- date

Not sure at this time how rundeck goes about listing nodes and all that entails.
This might help with this http://rundeck.org/docs/administration/managing-node-sources.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants