<p>I am trying to learn the implementation of CI/CD pipeline using Jenkins and Kubernetes for my Spring Boot microservice deployment.</p>

<p>I following the following links for references,</p>

<ol>
<li><a href="https://dzone.com/articles/easily-automate-your-cicd-pipeline-with-jenkins-he" rel="nofollow noreferrer">https://dzone.com/articles/easily-automate-your-cicd-pipeline-with-jenkins-he</a></li>
<li><a href="https://medium.com/jfrogplatform/easily-automate-your-ci-cd-pipeline-with-jenkins-helm-and-kubernetes-c96283c25701" rel="nofollow noreferrer">https://medium.com/jfrogplatform/easily-automate-your-ci-cd-pipeline-with-jenkins-helm-and-kubernetes-c96283c25701</a></li>
</ol>

<p>Here I am finding the way that to use Kubernetes Helm chart for simplifying application deployment. In the aboev link it showing that, to use one Helm repository along with Docker registry (I am planning to use Dockerhub.com).</p>

<p><strong>Confusion</strong></p>

<p>Here my confusion is that, If we are using Helm chart with Kubernetes, then why to use Helm repository for my CI/CD pipeline?</p>

<p>You could work with your helm charts unpackaged, effectively deploying them from source. You don't <em>necessarily</em> have to package them and host them in a repo. You probably will want to package the charts and host them in a repo if you have multiple apps/teams consuming the charts and perhaps building their own charts using them and/or you want to be able to have different versions of a chart running in different places. </p>
