{
  "digest": "sha256:b02017781eadbcd6085cc2349de5f8a21454b61d5d3ea31234663cbf606b2b19",
  "mediaType": "application/vnd.oci.image.manifest.v1+json",
  "size": 1392,
  "config": {
    "digest": "sha256:d52a3a160b17ff307de7687f48941c24195aaddc8726873969e1dab72b134c00",
    "mediaType": "application/vnd.cncf.helm.config.v1+json",
    "size": 1055
  },
  "layers": [
    {
      "digest": "sha256:d52a3a160b17ff307de7687f48941c24195aaddc8726873969e1dab72b134c00",
      "mediaType": "application/octet-stream",
      "size": 1055
    },
    {
      "digest": "sha256:d6bd7b0eaebdcd41b13d3e164fcb51f721904a4d7f44d1ec546a73e69196bfa6",
      "mediaType": "application/vnd.cncf.helm.chart.content.v1.tar+gzip",
      "size": 8675
    }
  ],
  "labels": {
    "org.opencontainers.image.description": "A chart to install node-local-dns.  NodeLocal DNSCache improves Cluster DNS performance by running a DNS caching agent on cluster nodes as a DaemonSet.  In today's architecture, Pods in 'ClusterFirst' DNS mode reach out to a kube-dns serviceIP for DNS queries. This is translated to a kube-dns/CoreDNS endpoint via iptables rules added by kube-proxy. With this new architecture, Pods will reach out to the DNS caching agent running on the same node, thereby avoiding iptables DNAT rules and connection tracking. The local caching agent will query kube-dns service for cache misses of cluster hostnames (\"cluster.local\" suffix by default).  Further documentation is [here](https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/)  This helm chart works for both kube-proxy setups (iptables or ipvs). ",
    "org.opencontainers.image.title": "node-local-dns",
    "org.opencontainers.image.authors": "gabrieladt (no-reply@deliveryhero.com)",
    "org.opencontainers.image.version": "2.1.0"
  }
}