{"id":7367,"date":"2022-05-20T09:10:00","date_gmt":"2022-05-20T08:10:00","guid":{"rendered":"https:\/\/telecomkh.info\/?p=7367"},"modified":"2022-05-20T09:11:12","modified_gmt":"2022-05-20T08:11:12","slug":"pull-based-kubernetes-deployments-moving-to-gitlab-free-tier","status":"publish","type":"post","link":"https:\/\/telecomkh.info\/?p=7367","title":{"rendered":"Pull-based Kubernetes deployments moving to GitLab Free tier"},"content":{"rendered":"

GitLab will include support for pull-based deployment in the platform\u2019s Free tier in an upcoming release, which will provide users increased flexibility, security, scalability, and automation in cloud-native environments<\/strong><\/p>\n

 <\/p>\n

By Sandra Gittlen and Lauren Minning<\/em><\/span><\/p>\n

With pull-based deployment, DevOps teams can use the GitLab agent for Kubernetes to automatically identify and enact application changes. \u201cDevOps teams at all levels benefit from utilizing GitOps strategies such as pull-based deployment in their cloud-native environments. By offering this feature in GitLab\u2019s Free tier, we can introduce more organizations to the power and utility of this secure and scalable functionality,\u201d says Viktor Nagy, product manager of GitLab\u2019s Configure Group.
\nAs an open-core company, GitLab is happy to contribute to the GitOps community and enable the adoption of best practices in the industry.<\/p>\n

What is pull-based deployment?<\/strong>
\nPull-based and push-based deployment are two main approaches to GitOps, an operational framework that takes DevOps best practices used for application development such as version control, collaboration, compliance, and CI\/CD tooling, and applies them to infrastructure automation.
\nGitOps enables operations teams to move as quickly as their application development counterparts by making use of automation and scalability, without sacrificing security.
\nWhile push-based, or agentless, deployment relies on a CI\/CD tool to push changes to the infrastructure environment, pull-based deployment uses an agent installed in a cluster to pull changes whenever there is a deviation from the desired configuration. In the pull-based approach, deployment targets are limited to Kubernetes and an agent must be installed in each Kubernetes cluster.
\n\u201cAs long as the GitLab agent for Kubernetes on your infrastructure has the necessary access rights in your cluster, you can configure everything automatically, reducing the DevOps workload and the opportunity to introduce errors,\u201d Nagy says.<\/p>\n

Pull-based deployment vs. push-based deployment<\/strong><\/p>\n

Push-based deployment and pull-based deployment each have their pros and cons.
\nHere is a list of the advantages and disadvantages of each GitOps practice:<\/p>\n

Push-based deployment pros:
\n\u25cf ease of use
\n\u25cf well-known as part of CI\/CD
\n\u25cf more flexible, as deployment targets can be on physical servers or virtual containers, not restricted to Kubernetes clusters<\/p>\n

Push-based deployment cons:
\n\u25cf requires organizations to open their firewall to a cluster and grant admin access to external CI\/CD<\/p>\n

\u25cf requires organizations to adjust their CI\/CD pipelines when they introduce new environments<\/p>\n

Pull-based deployment pros:
\n\u25cf secure infrastructure – no need to open your firewall or grant admin access externally
\n\u25cf changes can be automatically detected and applied without human intervention easier scaling of identical clusters<\/p>\n

Pull-based deployment cons:
\n\u25cf agent needs to be installed in every cluster limited to Kubernetes only<\/p>\n

How pull-based deployment impacts the Free-tier experience<\/strong>
\nIncluding support for pull-based deployments in GitLab\u2019s Free tier provides a tremendous competitive advantage for smaller organizations, as they can now apply automation in a safe and scalable manner to their cloud-native infrastructure, including virtual containers and clusters. And, for organizations that are trying to get started quickly by minimizing the number of tools in their infrastructure ecosystem, this functionality is included in One DevOps Platform, not as a point solution.
\n\u201cDevOps teams don\u2019t have to continuously write code for new infrastructure elements \u2013 they can write the code once, within a single DevOps platform, and have the agent automatically find it, pull it, and apply it, as well as configuration changes,\u201d Nagy says.
\n\u201cAlso, with the availability of pull-based deployment in this introductory tier, newcomers to GitLab will immediately be able to modernize application development and reduce the security risk associated with configuring such infrastructure.\u201d<\/p>\n

Above, GitLab at KubeCon + CloudNativeCon Europe 2022 – Image credited to telecomkh<\/em><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

GitLab will include support for pull-based deployment in the platform\u2019s Free tier in an upcoming release, which will provide users increased flexibility, security, scalability, and automation in cloud-native environments   By Sandra Gittlen and Lauren Minning With pull-based deployment, DevOps teams can use the GitLab agent for Kubernetes to automatically identify and enact application changes. … <\/p>\n

Continue reading \u00abPull-based Kubernetes deployments moving to GitLab Free tier\u00bb<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":7368,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[67],"tags":[],"_links":{"self":[{"href":"https:\/\/telecomkh.info\/index.php?rest_route=\/wp\/v2\/posts\/7367"}],"collection":[{"href":"https:\/\/telecomkh.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomkh.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomkh.info\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomkh.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7367"}],"version-history":[{"count":1,"href":"https:\/\/telecomkh.info\/index.php?rest_route=\/wp\/v2\/posts\/7367\/revisions"}],"predecessor-version":[{"id":7369,"href":"https:\/\/telecomkh.info\/index.php?rest_route=\/wp\/v2\/posts\/7367\/revisions\/7369"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/telecomkh.info\/index.php?rest_route=\/wp\/v2\/media\/7368"}],"wp:attachment":[{"href":"https:\/\/telecomkh.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomkh.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomkh.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}