cstor-operators
external-dns
Our great sponsors
cstor-operators | external-dns | |
---|---|---|
4 | 79 | |
93 | 7,232 | |
- | 1.6% | |
5.1 | 9.6 | |
3 months ago | 7 days 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.
cstor-operators
-
Why OpenEBS 3.0 for Kubernetes and Storage?
OpenEBS CStor (declared stable), has added support for a CSI Driver and also improved customer resources and operators for managing the lifecycle of CStor Pools. This 3.0 version of the CStor includes:
-
32 Node KBN-I/5200 Kubernetes cluster running Debian 10/K8s 1.17/Intel Core i7/8GB RAM each. Used the standoffs and mounted each 8 stack to empty trays. Disks are 64GB USB3 sticks.
It's a little complicated at first but there's also OpenEBS and Longhorn. Longhorn is probably the most easiest to get going with, but I chose rook-ceph because it's very stable.
-
Looking for a sanity check on a project I'm working on at home, hoping you fine people can help - Raspberry Pi Kubernetes Cluster
- SMB CSI: https://github.com/kubernetes-csi/csi-driver-smb - OpenEBS if you got the hardware for it: https://openebs.io/
-
Best Open-Source Distributed Parallel Storage Option for an AI/ML Cluster?
Tried OpenEBS? These two have replication HA features. https://github.com/openebs/Mayastor https://github.com/openebs/cstor-operators
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?
Mayastor - Dynamically provision Stateful Persistent Replicated Cluster-wide Fabric Volumes & Filesystems for Kubernetes that is provisioned from an optimized NVME SPDK backend data storage stack.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
jiva-operator - Kubernetes Operator for managing Jiva Volumes via custom resource.
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
openebs - Most popular & widely deployed Open Source Container Native Storage platform for Stateful Persistent Applications on Kubernetes.
ingress-nginx - Ingress-NGINX Controller for Kubernetes
longhorn - Cloud-Native distributed storage built on and for Kubernetes
crossplane - The Cloud Native Control Plane
zfs-localpv - Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend ZFS data storage stack.
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
dynamic-nfs-provisioner - Operator for dynamically provisioning an NFS server on any Kubernetes Persistent Volume. Also creates an NFS volume on the dynamically provisioned server for enabling Kubernetes RWX volumes.
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖