<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Service on Samarthya</title><link>https://samarthya.me/tags/service/</link><description>Recent content in Service on Samarthya</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© Samarthya 2018-2026. All rights reserved.</copyright><lastBuildDate>Fri, 26 Nov 2021 06:07:36 +0000</lastBuildDate><atom:link href="https://samarthya.me/tags/service/index.xml" rel="self" type="application/rss+xml"/><item><title>Helm Test</title><link>https://samarthya.me/posts/helm-test/</link><pubDate>Fri, 26 Nov 2021 06:07:36 +0000</pubDate><guid>https://samarthya.me/posts/helm-test/</guid><description>&lt;p&gt;The only advice I can give to folks who are building helm charts from scratch, is always keep it incremental and do not try to do everything at one go. At least build a decent few before you even try to attempt such a thing, else you will only end up WASTING your precious time on trivial issues which could have been avoided by incremental build, rather than the big bang approach.&lt;/p&gt;</description></item><item><title>K8S: Deployment</title><link>https://samarthya.me/posts/k8s-deployment/</link><pubDate>Tue, 22 Dec 2020 12:45:09 +0000</pubDate><guid>https://samarthya.me/posts/k8s-deployment/</guid><description>&lt;p&gt;Time to re-test how to create deployments. It has been sometime, I created some deployments so just checking on how much I remember.&lt;/p&gt;&#10;&lt;p&gt;The quick way to always get started is to check the &lt;code&gt;HELP&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Services: K8S</title><link>https://samarthya.me/posts/services-k8s/</link><pubDate>Fri, 21 Aug 2020 17:34:29 +0000</pubDate><guid>https://samarthya.me/posts/services-k8s/</guid><description>&lt;p&gt;There are multiple &lt;code&gt;Kubernetes&lt;/code&gt; objects we will be talking about in this blog. Mainly Services, Selectors and Labels.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Service is an abstraction which defines a logical set of Pods and a policy by which to access them.&lt;/li&gt;&#10;&lt;li&gt;A Service in Kubernetes is a REST object, similar to a Pod.&lt;/li&gt;&#10;&lt;li&gt;Service tags the pods, logically grouping them using selectors.&lt;/li&gt;&#10;&lt;li&gt;Pods have a lifecycle, they are born, they live, process and then they die. The pods (desired state) can be managed using deployment.&lt;/li&gt;&#10;&lt;li&gt;A label is an identifying attribute of an object, and can be defined at the creation time, and subsequently modified and added at any time.&lt;/li&gt;&#10;&lt;li&gt;Label selector is a grouping primitive in Kubernetes and allows client/user to identify a set of objects. There are two sets of selectors&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;em&gt;equality-based&lt;/em&gt; and&lt;/li&gt;&#10;&lt;li&gt;&lt;em&gt;set-based&lt;/em&gt;.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; An abstract way to expose an application running on a set of &lt;a href="https://kubernetes.io/docs/concepts/workloads/pods/" target="_blank" rel="noreferrer"&gt;Pods&lt;/a&gt; as a network service.&#10;&lt;/div&gt;&#10;&#10;&lt;p&gt;The set of Pods targeted by a Service is usually determined by a selector.&lt;/p&gt;</description></item></channel></rss>