external-dns
charts
DISCONTINUED
Our great sponsors
external-dns | charts | |
---|---|---|
78 | 28 | |
7,188 | 15,373 | |
2.7% | - | |
9.6 | 2.1 | |
7 days ago | about 2 years ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
external-dns
-
Kubernetes External DNS provider for Hetzner
One of the reasons why I chose Hetzner was that it WAS supported by the ExternalDNS project. I didn't quite understand why the Hetzner provider was pulled, but I saw that an attempt of re-adding it was refused, on the ground that the upcoming webhook architecture would have allowed to better maintain providers.
-
I am stuck on learning how to provision K8s in AWS. Security groups? ALB? ACM? R53?
So here’s the solution I have taken for our current stack. EKS and its dependencies are created through terraform using the eks module as well as provision a route53 subdomain and a wildcard cert. Once we have that created, I have installed this deployment into the cluster via the helm module: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/. This allows me to use kuberentes resources (load balancers or ingress objects) and it will handle all the provisioning of load balancers and security groups for me, based on my application yaml and annotations. We also use https://github.com/kubernetes-sigs/external-dns to manage all of our specific host names for the applications through annotations. So to generally put, terraform manages out Kubernetes clusters, and Kubernetes manages the deployment of anything needed for the application including volumes, load balancers, hostnames though Kubernetes system deployments
-
Kubernetes as a Platform vs. Kubernetes as an API
Disclaimer: I work for AWS but had nothing to do with this blog post (I'm seeing it for the first time with everyone else here).
I think this is an unfair summary of the post. Of course, using Kubernetes to orchestrate other AWS services is going to be a go-to example on the _AWS_ blog, but there is plenty of vendor-agnostic software doing similar things: DNS Records[1], Databases[2], even using Kubernetes CRDs to deploy Kubernetes[3].
The idea of using Kubernetes as an API to orchestrate external resources doesn't inherently lock you into any single vendor.
-
Does it make sense to use nginx on top of the ingress-nginx
For the average developer an Ingress is substantially simpler to understand. For an expert such as yourself there are additional annotations which may be added, to use nginx specfic features. However the big win using the nginx ingress controller is integration with other Kubernetes features like cert manager and External DNS
-
Kubernetes external-dns add support for pi-hole in the latest release
In the latest version v0.13.2 add support for pi-hole as a dns provider:
-
Help me understand real use cases of k8s, I can’t wrap my head around it
external-dns
- Dont understand how I can watch external resources modification/deletion with my custom operator
-
cloudflare and ingress-nginx
I can then set annotations on the Ingress resource to tell external-dns to flip the proxy switch on the DNS record in Cloudflare:
-
Istio woes on eks 1.22 - external-dns version stuck to v0.7.2
according to users in this issue they claim the external-dns image being a cause of their dns failing on kubernetes 1.22. https://github.com/kubernetes-sigs/external-dns/issues/961
charts
-
Loading Kibana dashboards using Metricbeat through HELM charts
I did this using the incubator/raw chart ( https://github.com/helm/charts/tree/master/incubator/raw ), by creating a k8s Job.
-
K8S - using Prometheus to monitor another prometheus instance in secure way
I've installed Prometheus operator 0.34 (which works as expected) on cluster A (main prom)Now I want to use the federation option,I mean collect metrics from other Prometheus which is located on other K8S cluster B
-
How to silence Prometheus Alertmanager using config files?
I'm using the official stable/prometheus-operator chart do deploy Prometheus with helm.
-
Prometheus Definitive Guide Part III - Prometheus Operator
Enter the default username: admin and password: prom-operator which you can find from here to access Grafana.
- Multipass, Microk8s, Prometheus and Grafana
- ECS migrate to EKS part 3
-
Deploying Jenkins on Google Cloud
In this step opta generates terraform code to deploys helm chart. You can review the plan and accept it. It will take around 2-3 minutes for the plan to get applied. For specifying values to the helm chart you can modify the values inside opta-gcp/opta.yml . Refer to jenkins helm chart for more details https://github.com/helm/charts/tree/master/stable/jenkins. After opta apply finishes you will have jenkins up and running on your infra.
-
k8s-secretgen: Got tired of generating secrets for testing stuff so I made a script to automate it.
I do use Helm to deploy, but the trouble with using it for secrets is that it overwrites them on an upgrade.
-
My Journey With Spark On Kubernetes... In Python (1/3)
In this section, you use Helm to deploy the Kubernetes Operator for Apache Spark from the incubator Chart repository. Helm is a package manager you can use to configure and deploy Kubernetes apps.
-
Autoscaling Redis applications on Kubernetes 🚀🚀
Redis: I have used Azure Cache for Redis, but feel free to explore other options e.g. you can install one in your Kubernetes cluster using a Helm chart).
What are some alternatives?
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
ingress-nginx - Ingress-NGINX Controller for Kubernetes
crossplane - The Cloud Native Control Plane
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
k3s - Lightweight Kubernetes
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
kubernetes-mixin - A set of Grafana dashboards and Prometheus alerts for Kubernetes.
kube-vip - Kubernetes Control Plane Virtual IP and Load-Balancer
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming [Moved to: https://github.com/cdk8s-team/cdk8s]
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes