<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>k8s on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/k8s/</link>
    <description>Recent content in k8s on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Wed, 24 Apr 2024 15:20:00 +0200</lastBuildDate><atom:link href="https://coredns.io/tags/k8s/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>k8s_cache</title>
      <link>https://coredns.io/explugins/k8s_cache/</link>
      <pubDate>Wed, 24 Apr 2024 15:20:00 +0200</pubDate>
      
      <guid>https://coredns.io/explugins/k8s_cache/</guid>
      <description>Description This is a fork of cache. It adds an option to send a refreshed positive cache item first to pods with the label k8s-cache.coredns.io/early-refresh=true. Other pods get it only after a specified duration. This makes it possible to implement stable NetworkPolicy whitelists on the basis of domain names that are resolved with DNS, using Stable FQDNNetworkPolicies.
The implementation uses an additional cache store called the &amp;ldquo;late cache&amp;rdquo;, which is shifted a number of seconds.</description>
    </item>
    
    <item>
      <title>k8s_gateway</title>
      <link>https://coredns.io/explugins/k8s_gateway/</link>
      <pubDate>Sat, 19 Sep 2020 12:00:00 -0800</pubDate>
      
      <guid>https://coredns.io/explugins/k8s_gateway/</guid>
      <description>Description This plugin is very similar to k8s_external but supporting all types of Kubernetes external resources - Ingress, Service of type LoadBalancer and networking.x-k8s.io/Gateway (when it becomes available).
This plugin relies on it&amp;rsquo;s own connection to the k8s API server and doesn&amp;rsquo;t share any code with the existing kubernetes plugin. The assumption is that this plugin can now be deployed as a separate instance (alongside the internal kube-dns) and act as a single external DNS interface into your Kubernetes cluster(s).</description>
    </item>
    
  </channel>
</rss>
