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
pipeline { agent { kubernetes { label 'parent-pod'
Or
pipeline { agent { mycloud { label 'parent-pod'
I can run agents on whatever cloud was configured in jenkins. This is the clean way to support multiple clouds according to the Jenkins Kubernetes plugin. This way some of the staging environments can be installed on different clusters. Of course therefore the agent will be executed on the target cluster. All the required information to connect to the target cluster are part of the standard kubernetes plugin.
The text was updated successfully, but these errors were encountered:
This is in planning, but not documented yet.
Basically it is also possible with the current solution because you can use your own templates with the "TEMPLATES_BASE_DIRECTORY" configuration. There you can add or copy and change the configuration templates you want and add as many clouds as you want.
But for better usability the solution should work like the cloud-templates with the possibility to select the cloud environments for special instances.
When specifying the following
pipeline { agent { kubernetes { label 'parent-pod'
Or
pipeline { agent { mycloud { label 'parent-pod'
I can run agents on whatever cloud was configured in jenkins. This is the clean way to support multiple clouds according to the Jenkins Kubernetes plugin. This way some of the staging environments can be installed on different clusters. Of course therefore the agent will be executed on the target cluster. All the required information to connect to the target cluster are part of the standard kubernetes plugin.
The text was updated successfully, but these errors were encountered: