Hi,

I am starting to ramp up some kubernetes cluster based worker nodes into an 
existing Jenkins master that uses Node Restrictions and labels to keep 
certain hands off of resources that aren't allotted to them.

I have a mixture of non-pipeline and pipeline projects.   I noticed the 
kubernetes plugin could cooperate with settings in folders to restrict the 
use of the cloud to certain pipeline projects.

In the Node configure dialog, with the Node Restriction option, I could 
specify a regex of all of the projects that were allowed to access the Node.

The Node Restriction option is blank for nodes spun up into kubernetes.

Besides recasting all of my non-pipeline projects into pipeline projects, 
is there another way to get the same effect?  Or a better way in general to 
handle this?

Project specific labels for nodes and different pod templates for each 
project?

Thanks,

- - - Philip

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6625f51c-3483-4801-acc4-57392cadb4f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to