kubernetes-plugin | Jenkins plugin to run dynamic agents | Continuous Deployment library

by jenkinsci Java Version: 3937.vd7b_82db_e347b_ License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | kubernetes-plugin Summary

kubernetes-plugin is a Java library typically used in Devops, Continuous Deployment, Docker applications. kubernetes-plugin has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can download it from GitHub.

Kubernetes plugin for Jenkins.

Support

Quality

Security

License

Reuse

Support

kubernetes-plugin has a medium active ecosystem.

It has 2193 star(s) with 1238 fork(s). There are 67 watchers for this library.

It had no major release in the last 12 months.

kubernetes-plugin has no issues reported. There are 25 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of kubernetes-plugin is 3937.vd7b_82db_e347b_

Quality

kubernetes-plugin has 0 bugs and 0 code smells.

Security

kubernetes-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

kubernetes-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

kubernetes-plugin is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

kubernetes-plugin releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

kubernetes-plugin saves you 8110 person hours of effort in developing the same functionality from scratch.

It has 17305 lines of code, 1428 functions and 275 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed kubernetes-plugin and discovered the below as its top functions. This is intended to give you an instant insight into kubernetes-plugin implemented functionality, and help decide if they suit your requirements.

Launches the agent
Create a container
Creates a map of environment variables to be used by the agent
Builds a pod from a pod template
Decorates the launcher with the given node
Execute the supplied commands
Returns a list of commands to execute a command
The start method
Recompute the set of labels derived from the label
Compares this template to another
Pop a namespace from the stack
Builds a plan
Checks if this port matches the specified port
Registers the executors for the specified pod
Join the websocket
Gets the events for the current pod
Set up credentials
Returns a hash code for this instance
Start the container step
Returns a list of containers in the cluster
Returns the arguments as arguments
Run the step
Checks if an error is detected
Resolves the container
Determine the capacity of the strategy
Terminates the agent

Get all kandi verified functions for this library.

kubernetes-plugin Key Features

No Key Features are available at this moment for kubernetes-plugin.

kubernetes-plugin Examples and Code Snippets

No Code Snippets are available at this moment for kubernetes-plugin.

Community Discussions

Trending Discussions on kubernetes-plugin

Jenkins K8s plugin WebSocket Timeout in container step

Unable to build Docker images through Jenkins installed on Kubernetes

hostPathVolume not mounting on Kubernetes pods(Dynamic Jenkins Agent)

Use "label" or define a pod template in jenkinsfile for kubernetes-plugin?

When I use Kubernetes as my agent in Jenkins it will not allow another executor in stage

QUESTION

Jenkins K8s plugin WebSocket Timeout in container step

Asked 2022-Jan-10 at 10:39

I have created a K3d cluster. I've Deployed a jenkins 2.319.1 controller inside, along with kubernetes plugin 1.31.1 (and git, pipeline and the like) The idea is to run both the controller and the agents in the same cluster. To do so I've configured a cloud like in this picture: [Cloud Configuration ][1] [1]: https://i.stack.imgur.com/u91Fr.png

(I've done several attempts with different combinations for the agents to connect to the controller. Finally I've stayed with JNLP - NO WEBSOCKET - although, anyway, the timeout I'm about to describe is common to both of them)

With the cloud configured and being able to spawn the agents, after many attempts I finally discovered that the job was hanging (and dying of timeout) in the execution inside a container step. Actions within the default "jnlp" container are ok but the moment you do something as trivial as: sh 'ls -l' inside another container the job dies after 30 seconds with the following log:

...

ANSWER

Answered 2022-Jan-10 at 10:39

As mentioned in previous comment referring to post (Jenkins with Kubernetes Client Plugin - NoSuchMethodError) upgrading kubernetes plugin to v1.31.2 solved the problem. Already patched and tested.

Source https://stackoverflow.com/questions/70594628

QUESTION

Unable to build Docker images through Jenkins installed on Kubernetes

Asked 2021-May-03 at 05:16

I used the following helm chart to install Jenkins

https://artifacthub.io/packages/helm/jenkinsci/jenkins

The problem is it does't build docker images, saying there's no docker. Docker was installed on host with sudo apt install docker-ce docker-ce-cli containerd.io

...

ANSWER

Answered 2021-Apr-08 at 20:25

You are running Jenkins itself as a container. Therefore the docker command line application must be present in the container, not the host.

Easiest solution: Use a Jenkins docker image that contains the docker cli already, for example https://hub.docker.com/r/trion/jenkins-docker-client

Source https://stackoverflow.com/questions/67011315

QUESTION

hostPathVolume not mounting on Kubernetes pods(Dynamic Jenkins Agent)

Asked 2020-Dec-07 at 04:53

Environment: 
Jenkins - Version 2.235.5 (LTS)
Kubernetes Jenkins Plugin  - 1.27.7

K8s-Master & Worker Server Details:-
OS - CentOS Linux release 7.9.2009 (Core) & Kernal - 3.10.0-1160.6.1.el7.x86_64
Docker Version - 19.03.12
Client Version: v1.19.0
Server Version: v1.19.0

...

ANSWER

Answered 2020-Dec-07 at 04:53

I have upgraded my docker image from Ubuntu 16.04.6 LTS - 3.10.0-1160.6.1.el7.x86_64 to Ubuntu 16.04.7 to 3.10.0-1160.6.1.el7.x86_64 still didn't work. But it seems Kubernetes on CentOS-7.9 & with Kernal-3.10.0-1160.6.1.el7.x86_64 is having kernel specific issue. So i have upgraded my native host's OS to CentOS-8.2 with - 4.18.0-193.28.1.el8_2.x86_64 kernel, Now my pipeline build working fine.

Source https://stackoverflow.com/questions/65153670

QUESTION

Use "label" or define a pod template in jenkinsfile for kubernetes-plugin?

Asked 2020-Apr-23 at 14:03

In General

I'm trying to use label when using kubernetes-plugin for Jenkins, but I get a little bit confused. In my pipeline bellow I'm trying to build test job in parallel steps with different labels (agents).

I already have configured the plugin with pod template and container in my Jenkins config, where I use same settings as it's in the pipeline podTemplate defined.

Issue

The problem is that when I use agent label in stage 2 there is jnpl image running instead the image that I point in the config someimage:latest.

In stage 1 where I define the pod in pipeline there is no problem and the required images are running fine.

Question

What I'm doing wrong? Here is my jenkinsfile and config of the kubernetes-plugin in Jenkins:

...

ANSWER

Answered 2020-Apr-23 at 14:03

You did not specified an image for stage with label k8s and windows.

You can read in the docs that:

The plugin creates a Kubernetes Pod for each agent started, defined by the Docker image to run, and stops it after each build.

Agents are launched using JNLP, so it is expected that the image connects automatically to the Jenkins master.

You are using podTemplate and I would advice setting up container , this might look like the following:

Source https://stackoverflow.com/questions/61385922

QUESTION

When I use Kubernetes as my agent in Jenkins it will not allow another executor in stage

Asked 2020-Mar-13 at 13:24

This is a subset of my declarative Jenkinsfile:

...

ANSWER

Answered 2020-Mar-13 at 13:24

Actually I manage to solve this while I was asking it. Don't use a defaultContainer when declaring the root agent and tell explicitly which container you want to use in every stage:

Source https://stackoverflow.com/questions/60671321

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install kubernetes-plugin

You can download it from GitHub.
You can use kubernetes-plugin like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the kubernetes-plugin component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: