Find the ID :
# mysqladmin processlist -hmysql-service -uroot -proot_password
Kill the process :
Setup tiller in your k8s cluster as here - https://gist.github.com/vishnuhd/08a5b830a4dbf2476ee40ace18e36a31
Create jenkins namespace
kubectl create ns jenkins
jenkins
namespace.k8s.local
and before that you can put almost anything.➜ curl -X GET http://localhost:8080/job/test-pipeline/config.xml -u admin:admin -o config.xml
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1599 100 1599 0 0 18518 0 --:--:-- --:--:-- --:--:-- 18593
➜ CRUMB=$(curl -s 'http://localhost:8080/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)' -u admin:admin)
Since CoreOS coined the term "Operator", their article is the authority on what they mean by that:
An Operator is an application-specific controller that extends the Kubernetes API to create, configure and manage instances of complex stateful applications on behalf of a Kubernetes user. It builds upon the basic Kubernetes resource and controller concepts, but also includes domain or application-specific knowledge to automate common tasks better managed by computers.
We use Operators because managing stateful applications, like databases, caches and monitoring systems, is a big challenge, especially at massive scale. These systems require human operational knowledge to correctly scale, upgrade and reconfigure while at the same time protecting against data loss and unavailability.
To paraphrase: All Operators use the controller pattern, but not all controllers are Operators. It's only an Operator if it's got: controller pattern + API extension + single-app focus.
TfJob is a good example of an Operator,
Command :
docker run -d -v jenkins_home:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock -p 8080:8080 -p 50000:50000 jenkins/jenkins:lts
PS :
Docker should be installed on the host machine.
Install Helm using the Helm installation instructions.
kubectl create serviceaccount tiller -n kube-system
kubectl create clusterrolebinding tiller \
--clusterrole=cluster-admin \