local-path-provisioner
cdk8s
Our great sponsors
local-path-provisioner | cdk8s | |
---|---|---|
30 | 48 | |
1,982 | 4,115 | |
3.3% | 2.3% | |
6.3 | 9.7 | |
21 days ago | 8 days ago | |
Go | JavaScript | |
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
cdk8s
-
K8s Service Meshes: The Bill Comes Due
Any, it doesn’t matter which as long as you don’t have to count spaces in yaml by hand.
If you really want a concrete recommendation try https://cdk8s.io/.
- Why the fuck are we templating YAML? (2019)
- Cdk8s: Kubernetes native apps and abstractions using object-oriented programming
-
10 Ways for Kubernetes Declarative Configuration Management
CDK8s - CDK8s is used to define Kubernetes resources and applications. CDK8s uses the high-level abstraction concept called constructs to represent various Kubernetes resources such as deployments, services, and configurations. Developers can write code in programming languages like TypeScript, Python, and Java, and CDK8s will translate this code into standard Kubernetes YAML manifests that can be directly applied to a Kubernetes cluster.
-
I built a React renderer for Kubernetes configurations
Have you looked into https://cdk8s.io/? I've been using it for a while now, and I must admit TypeSript does help a lot. Not really sold on your React syntax yet, but well done nevertheless
-
How are most EKS clusters deployed?
I, personally, prefer to wrap it in CDKTF/CDK8S in golang and manage with Crossplane Composition Functions, but your mileage may vary. I'm finding way too bugs in CDK's... but it calms me a bit, that Amazon folks actually looking into it.
-
Editing Badly formatted yaml file
Have you looked into cdk8s? That will let you get away from dealing with yaml and let you use code instead. Helm included.
-
kpt, cue, ... Your experiences?
My favorite is cdk8s + typescript.
- Cloud Development Kit for Kubernetes
-
Dump Kustomize with 20 lines of TypeScript
What about https://cdk8s.io/?
What are some alternatives?
sig-storage-local-static-provisioner - Static provisioner of local volumes
helmfile - Deploy Kubernetes Helm Charts
topolvm - Capacity-aware CSI plugin for Kubernetes
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
jsonnet - Jsonnet - The data templating language
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way. No scripts.