charts
DISCONTINUED
external-dns
Our great sponsors
charts | external-dns | |
---|---|---|
30 | 78 | |
1,367 | 7,188 | |
- | 2.7% | |
9.7 | 9.6 | |
over 1 year ago | 7 days ago | |
Smarty | 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.
charts
- Helm charts that bundles basic home server apps?
-
Getting Started with Kubernetes Questions
Spinning up workloads in kubernetes is much different than just spinning up a container in docker or even with docker compose. If someone has not already packaged it in a helm chart or some other kubernetes workload you'll have to develop one yourself. There are some nice library charts you can use as a base that should handle just about any random docker image you want to deploy. https://github.com/bjw-s/helm-charts/tree/main/charts/library/common there is also a repo of pre developed charts for common images. https://github.com/k8s-at-home/charts but be aware it was recently deprecated so it won't be receiving any updates.
-
Advice on system design best practices?
Take a look at https://github.com/k8s-at-home/charts (recently deprecated but still a fantastic resource) - there are charts for the popular Arrs , tools, etc. You could deploy each chart individually into a namespace, or you could create yourself an "umbrella" chart which pulls in all the necessary charts as dependencies.
-
With multiple custom apps, how do you manage your Helm charts?
Library charts. A very thorough example can be seen here and usages of it here.
-
Struggling with Fireflyi-III installation
I'd submitted a helm chart at https://github.com/k8s-at-home/charts/tree/master/charts/stable/firefly-iii if you want to try out
- Plex on Kubernetes with hardware decoding... Victory
-
[Help!] K3s Sonarr failing with X509CertificateValidationService due to expired LetsEncrypt cert in Mono
I know /u/stefantigro means well but the way you are both doing the helm charts is not ideal, helm charts are meant to be shared, not as a means to install apps into your cluster from a local folder. While they can be, it's not a good pattern. Take the helm chart from here for example. This is a published helm chart you can install using the commands in the Readme and you only need to provide the configuration for your instance from the values.yaml file. You can take a look at the values I use for this helm chart here. You can also see I'm using an custom Sonarr image, this image is tailored to running in Kubernetes
-
Bounty for Homebridge TrueChart
There is a working Helm chart for k8s-at-home that should be a good starting point. The biggest hurdle I see is that homebridge can conflict with SCALE's mDNS service as seen in this linked post.
-
Been self-hosting close to half a year now. All running on a k3s cluster of raspberry pis. Thank you to this subreddit for all the help and great ideas!
There's an actual helm chart published here.
-
Does anybody else find Helm charts pretty useless?
Maybe you should checkout: https://github.com/k8s-at-home/charts
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
What are some alternatives?
truecharts - Community App Catalog for TrueNAS SCALE [Moved to: https://github.com/truecharts/charts]
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
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
MagicMirror - MagicMirror² is an open source modular smart mirror platform. With a growing list of installable modules, the MagicMirror² allows you to convert your hallway or bathroom mirror into your personal assistant.