terraform-cdk
external-dns
terraform-cdk | external-dns | |
---|---|---|
104 | 79 | |
4,727 | 7,266 | |
0.6% | 0.8% | |
9.8 | 9.6 | |
5 days ago | 3 days ago | |
TypeScript | Go | |
Mozilla Public 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.
terraform-cdk
-
Learning Go by examples: part 12 - Deploy Go apps in Go with CDK for Terraform (CDKTF)
At first I tested it to deploy an OVHcloud Managed Kubernetes Service (MKS) with a Node Pool. And step by step, it worked. I even created a Pull Request (PR) in the terraform-cdk repository to add it as an example ☺️.
-
AWS CDK For Noobs: Deploying NextJS Apps
I'll be trying more sample app deployments with CDK and maybe even explore CDK for Terraform.
-
Show HN: Winglang – a new Cloud-Oriented programming language
You can use CDK with other providers using https://github.com/hashicorp/terraform-cdk
In my experience, CDK is far better than Pulumi, especially if you're mostly going to be using AWS.
- Terraform CDK
-
Why is Kubernetes adoption so hard?
I, personally, prefer Crossplane Composite Functions on top of CDK8S, but had dropped CDKTF due to bloat. You can actually manage Kubernetes updates/upgrade lifecycle with Crossplane, as well.
- Cloud, Why So Difficult?
- What are some harsh truths that r/devops needs to hear?
-
Backend engineers that don't like JavaScript
I was going to recommend Pulumi, but looks like CDK for Terraform is still being kept up to date.
-
Should i migrate from Kustomize to Helm?
Avoid Pulumi, get directly to source and use https://github.com/hashicorp/terraform-cdk
- AWS IAM Roles, a tale of unnecessary complexity
external-dns
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
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.
-
Istio Multi-Cluster Setup
Write a custom controller for the external DNS controller, or setup some form of ArgoCD app / appset templating.
-
Looking for ExternalDns alternative for non k8s environment
so I am looking at having an automated way for new routers registered in Traefik to also have the corresponding DNS entry added to my Pihole instance similar to external-dns but obviously, this is exclusive to ingress on k8s environments. my current setup is traefik in a container on unraid.
-
Is a Load Balancer necessary for a HA Cluster?
You technically don’t need to run a load balancer or have a virtual IP for your control plane. If you control your dns, you can add an A record pointing to all IPs for your control plane nodes. It won’t load balance your traffic, but combined with something like External DNS it gives you HA for the control plane.
-
How can I assign an EIP to a Kubernetes deployment?
I normally deploy external-dns, which automatically updates DNS with the ingress controller's external IP address.
-
Registering DNS with Windows Domain DNS
Background: Having a look I can see this https://github.com/kubernetes-sigs/external-dns
-
Cluster nodes on different networks
3) Use the Kubernetes External-DNS. I've never used this, but this is assuming it can update DNS for each pods/app to point to the correct Node (it'd need to update my Homelab DNS running on Windows Server)
-
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
-
How to expose services/apps to my home network with custom DNS names
Metallb for your load balancer (layer2 mode will do) NginX-ingress, will be spot on for internal home apps External-dns to publish your dns record to your Dns server at home, https://github.com/kubernetes-sigs/external-dns
What are some alternatives?
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
crossplane - The Cloud Native Control Plane
ingress-nginx - Ingress-NGINX Controller for Kubernetes
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
aws-cdk-local - Thin wrapper script for using the AWS CDK CLI with LocalStack
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖