<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Kubernetes API on Shubham Singh</title>
    <link>https://1shubham7.blog/tags/kubernetes-api/</link>
    <description>Recent content in Kubernetes API on Shubham Singh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://1shubham7.blog/tags/kubernetes-api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introduction to Kubernetes Native Policy Management with Kyverno</title>
      <link>https://1shubham7.blog/kyverno-intro/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/kyverno-intro/</guid>
      <description>Kyverno is a dynamic admission controller that can be used to govern and enforce how a Kubernetes cluster is used.
Admission Controllers Let&amp;rsquo;s first start with admission controllers since Kyverno is an admission controller. In Kubernetes admission controllers are used to intercept requests going to the API servier and one of the two or both the things with them - mutate or/and validate. Kubernetes comes up with built-in admission controllers. The issue with these built-in admission controllers is that they are highly specific and different organizations may have different use cases with admission contollers not being fulfilled by these built-in admission controllers, therefore, for meeting these requirements we have dynamic admission controllers that can be developed as extensions and can be run as webhooks configured at runtime.</description>
    </item>
    
  </channel>
</rss>
