local-path-provisioner
ingress-nginx
local-path-provisioner | ingress-nginx | |
---|---|---|
30 | 203 | |
2,003 | 16,664 | |
1.8% | 0.7% | |
6.1 | 9.6 | |
2 days ago | 8 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.
local-path-provisioner
-
Deploy Ghost with MySQL DB replication using helm chart
Deploy local-path-provisioner storage class but it does not support readwritemany so for high availability of your Kubernetes cluster better to use longhorn
-
lvp: Local Volume CSI Provisioner -- Dynamic PV Provisioning for your Home Cluster
I use this one. I'm waiting for the day it's combined with syncthing to sync across all nodes. https://github.com/rancher/local-path-provisioner
-
issues with pv retaining data on local-path SC
So I have this single node k3s cluster. k3s uses local-path (https://github.com/rancher/local-path-provisioner) as default SC that allows one to create dynamic volumes using nodes local storage.
-
How to format drives for local persistent volumes
Just create 1 single partition and format it with whatevery filesystem you like. And then use ranchers local-path-provisioner which will create a folder per PV (k3s has this integrated by default).
-
Persisting data in a dynamic volume?
Tinkering locally with local path provisioner (https://github.com/rancher/local-path-provisioner), I find that I can delete and re-create the pod, and the data persists on disk. However, if I delete the PVC, when I recreate the PVC, a new directory on disk is created.
-
Issues with "victoria-metrics-k8s-stack", monitoring k8s targets
It is better to use https://github.com/rancher/local-path-provisioner (or similar) for this case which will do PVC on local directories because manually linking PV<>PVC will not work.
-
single node k8s on nuc - homelab/prod - storage question
Since you only have one physical node anyway, I would just make the cluster a single-node cluster (1 VM) and use local storage on that VM. I’m biased though because this is what I do (I run K3s and use local path provisioner).
-
Using local disks for both K8s workloads, and exporting via SMB?
Rancher's Local Path Provisioner - From reading, seems to just use HostPath or Local PVs under the hood, but adds dynamic provisoning
-
Kubernetes: How to Persistent Storage
With any of those tools, you'd implement a network storage on top of a network storage. I would go with mouting few volumes per node +local storage like (https://github.com/rancher/local-path-provisioner).
- There doesn't seam to be any good distributed block storage for Kubernetes
ingress-nginx
-
Automating EKS Deployment and NGINX Setup Using Helm with AWS CDK in Python
# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )
-
deploying a minio service to kubernetes
ingress-nginx
-
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.
-
[06/52] Accessible Kubernetes with Terraform and DigitalOcean
resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }
-
Deploy Ghost with MySQL DB replication using helm chart
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml
-
Kubernetes Gateway API v1.0: Should You Switch?
For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.
- nginx ingress controller installation
-
IP-Whitlisting: Is adjusting nginx-ingress-controller service a solution?
The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace
-
Deploy Rancher on AWS EKS using Terraform & Helm Charts
helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list
-
☸️ Kubernetes NGINX Ingress Controller: 10+ Complementary Configurations for Web Applications
Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.
What are some alternatives?
sig-storage-local-static-provisioner - Static provisioner of local volumes
traefik - The Cloud Native Application Proxy
topolvm - Capacity-aware CSI plugin for Kubernetes
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
haproxy-ingress - HAProxy Ingress
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
application-gateway-kubernetes-ingress - This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.