Displaying 1 to 9 from 9 results

external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services

  •    Go

ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers. Inspired by Kubernetes DNS, Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the Kubernetes API to determine a desired list of DNS records. Unlike KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly—e.g. AWS Route 53 or Google Cloud DNS.

cluster-proportional-autoscaler - Kubernetes Cluster Proportional Autoscaler Container

  •    Go

This container image watches over the number of schedulable nodes and cores of the cluster and resizes the number of replicas for the required resource. This functionality may be desirable for applications that need to be autoscaled with the size of the cluster, such as DNS and other services that scale with the number of nodes/pods in the cluster. Then install a release using the chart. The charts default values file provides some commented out examples for setting some of the values. There are several required values, but helm should fail with messages that indicate which value is missing.

gateway-api - Repository for the next iteration of composite service (e

  •    Go

The Gateway API is a part of the SIG Network, and this repository contains the specification and Custom Resource Definitions (CRDs). The latest supported version is v1alpha2 as released by the v0.4.0 release of this project. This version of the API is expected to graduate to beta in the future with relatively minimal changes.

network-policy-api - This repo addresses further work involving Kubernetes network security beyond the initial NetworkPolicy resource

  •    

The network policy API is a part of the SIG Network, and this repository addresses further work involving Kubernetes network security beyond the NetworkPolicy v1 resource. Learn how to engage with the Kubernetes community on the community page.




cluster-proportional-vertical-autoscaler

  •    Go

This container image watches over the number of nodes and cores of the cluster and resizes the resource limits and requests for a DaemonSet, ReplicaSet, or Deployment. This functionality may be desirable for applications where resources such as cpu and memory for a particular job need to be autoscaled with the size of the cluster. Please try out the examples in the examples folder.

ingress-controller-conformance - Repository for a compliance specification of ingress-controllers.

  •    Go

The goal of this project is to act as an executable specification in the form of a test suite, implementing a standard, actively maintained ingress-controller conformance specification. The conformance test suite will both ensure consistency across implementations, as well as simplify the work needed for other implementations to conform to the specification.

ip-masq-agent - Manage IP masquerade on nodes

  •    Go

The ip-masq-agent configures iptables rules to MASQUERADE traffic outside link-local (optional, enabled by default) and additional arbitrary IP ranges. It creates an iptables chain called IP-MASQ-AGENT, which contains match rules for link local (169.254.0.0/16) and each of the user-specified IP ranges. It also creates a rule in POSTROUTING that jumps to this chain for any traffic not bound for a LOCAL destination.

iptables-wrappers - Wrapper scripts for using iptables in containers

  •    Shell

This repository consists of wrapper scripts to help with using iptables in containers. Specifically, it provides a wrapper script to select between the two modes of iptables 1.8 ("legacy" and "nft") at runtime, so that hostNetwork containers that examine or modify iptables rules will work correctly regardless of which mode the underlying system is using.


kpng - Reworking kube-proxy's architecture

  •    Go

The project will provide multiple components, with the core being the API watcher that will serve the global and node-specific sets of objects. More context can be found in the project's KEP.






We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.