<p>I've got my K8 cluster which I need to update with new deployments. If I had my jenkins container inside the kluster itself, is this bad practice? The other option is to have a seperate server that ssh's inside my remote K8 cluster and handles new deployments then.</p>
<p>I've looked at this jenkins plugin <a href="https://plugins.jenkins.io/kubernetes-cd/" rel="nofollow noreferrer">https://plugins.jenkins.io/kubernetes-cd/</a> to handle the CI/CD process.</p>

<p>It is a good practice to use CI/CD - good start. I wouldn't say it is a &quot;bad practice&quot; to run Jenkins as a container on Kubernetes - but my experience is that it does not work very well, mostly because Jenkins is not designed for being run as a container on Kubernetes.</p>
<p>There are more modern alternatives, that is designed for containers and Kubernetes. <a href="https://jenkins-x.io/" rel="nofollow noreferrer">Jenkins X</a> is the next-gen version of Jenkins that is designed to be run on Kubernetes, see <a href="https://medium.com/@jdrawlings/serverless-jenkins-with-jenkins-x-9134cbfe6870" rel="nofollow noreferrer">Serverless Jenkins with Jenkins X</a> on how it is different from Jenkins.</p>
<p>Jenkins X is <a href="https://jenkins-x.io/blog/2020/03/11/tekton/" rel="nofollow noreferrer">built on-top of Tekton</a>, another Kubernetes native CI/CD <a href="https://tekton.dev/" rel="nofollow noreferrer">project</a> and Tekton can be run standalone as well, using <a href="https://github.com/tektoncd/pipeline" rel="nofollow noreferrer">Tekton Pipelines</a>, <a href="https://github.com/tektoncd/triggers" rel="nofollow noreferrer">Tekton Triggers</a> and <a href="https://github.com/tektoncd/dashboard" rel="nofollow noreferrer">Tekton Dashboard</a>. Tekton is a very active community, backed by <a href="https://cloud.google.com/tekton" rel="nofollow noreferrer">Google</a> and Red Hat and more companies to provide a great CI/CD solution designed to work on Kubernetes.</p>
