zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
2.3 KiB
Contributing Guidelines
Welcome to Kubernetes. We are excited about the prospect of you joining our community! The Kubernetes community abides by the CNCF code of conduct. Here is an excerpt:
As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
Criteria for adding code here
This library adapts the stdlib encoding/json decoder to be compatible with
Kubernetes JSON decoding, and is not expected to actively add new features.
It may be updated with changes from the stdlib encoding/json decoder.
Any code that is added must:
- Have full unit test and benchmark coverage
- Be backward compatible with the existing exposed go API
- Have zero external dependencies
- Preserve existing benchmark performance
- Preserve compatibility with existing decoding behavior of
UnmarshalCaseSensitivePreserveInts()orUnmarshalStrict() - Avoid use of
unsafe
Getting Started
We have full documentation on how to get started contributing here:
- Contributor License Agreement Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests
- Kubernetes Contributor Guide - Main contributor documentation, or you can just jump directly to the contributing section
- Contributor Cheat Sheet - Common resources for existing developers
Community, discussion, contribution, and support
You can reach the maintainers of this project via the sig-api-machinery mailing list / channels.
Mentorship
- Mentoring Initiatives - We have a diverse set of mentorship programs available that are always looking for volunteers!