<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Soumik Majumder on Carvel</title><link>https://deploy-preview-832--carvel.netlify.app/blog/tags/Soumik-Majumder/</link><description>Recent content in Soumik Majumder on Carvel</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 19 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-832--carvel.netlify.app/blog/tags/Soumik-Majumder/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing kctrl package authoring commands</title><link>https://deploy-preview-832--carvel.netlify.app/blog/kctrl-pkg-authoring-cmds/</link><pubDate>Fri, 19 Aug 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-832--carvel.netlify.app/blog/kctrl-pkg-authoring-cmds/</guid><description>In today&amp;rsquo;s post, we are going to see how the kctrl CLI eases the process of package authoring.
A package is a combination of configuration metadata and OCI images. It informs the package manager what software it holds and how to install itself onto a Kubernetes cluster.
A package author encapsulates, versions and distributes Kubernetes manifests as package for package consumers to install on a Kubernetes cluster. They can choose to create a package by using a third party manifest like ones released by cert-manager, Dynatrace, etc.</description></item><item><title>Introducing kctrl, kapp-controller’s native CLI</title><link>https://deploy-preview-832--carvel.netlify.app/blog/kctrl-release-blog/</link><pubDate>Mon, 21 Mar 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-832--carvel.netlify.app/blog/kctrl-release-blog/</guid><description>kapp-controller provides declarative APIs to customise, install and update applications and packages reliably replicating workflows involving commonly used tools. It also allows authors of such workflows to package them and ship different versions of such workflows to consumers. The consumers in turn can consume these workflows using declarative APIs.
We realised that package consumers who are not comfortable with authoring YAMLs often face a steep learning curve while trying to get them up and running in their environments.</description></item><item><title>Making the most out of CLIs</title><link>https://deploy-preview-832--carvel.netlify.app/blog/making-the-most-out-of-clis/</link><pubDate>Mon, 21 Mar 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-832--carvel.netlify.app/blog/making-the-most-out-of-clis/</guid><description>Carvel is glad to have kapp and the (brand new!) kctrl as a part of our arsenal. In this blog, we will see how these powerful CLIs, along with our good old friend kubectl, fit into our day-to-day workflows.
We often see our users leverage all three of them in their workflows. Let&amp;rsquo;s look at what each one of them is super good at!
kubectl ¶kubectl is a CLI built by the Kubernetes team.</description></item><item><title>Using Carvel Terraform Provider to manage Kubernetes workloads</title><link>https://deploy-preview-832--carvel.netlify.app/blog/terraform-carvel-provider/</link><pubDate>Mon, 29 Nov 2021 00:00:00 +0000</pubDate><guid>https://deploy-preview-832--carvel.netlify.app/blog/terraform-carvel-provider/</guid><description>The Carvel tools are designed to empower our users to manage their Kubernetes workloads effectively. We realise that engineers leveraging Terraform to declaratively define their platforms might want to use Carvel tools to set up applications and workloads on their Kubernetes clusters in a predictable manner. Carvel&amp;rsquo;s terraform provider allows engineers to do exactly this using Terraform configurations.
In this blog, we will be using the provider to deploy this sample guestbook application on a Kubernetes cluster.</description></item></channel></rss>