https://github.com/cycoresystems/etcd-petset
Kubernetes PetSet for etcdv3
https://github.com/cycoresystems/etcd-petset
Last synced: 3 months ago
JSON representation
Kubernetes PetSet for etcdv3
- Host: GitHub
- URL: https://github.com/cycoresystems/etcd-petset
- Owner: CyCoreSystems
- Created: 2016-08-20T21:22:20.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2016-08-20T21:53:19.000Z (almost 10 years ago)
- Last Synced: 2026-01-27T14:48:30.327Z (5 months ago)
- Size: 233 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Example Kubernetes `PetSet` manifest for an `etcd` `PetSet`.
`PetSet`s are still very early types in Kubernetes, but we can get `etcd` up and
running with one, with a few particulars.
Of note:
- We must use the full DNS path for the peer URL, because the peer URL must
- be resolvable before the associated `Service` discovers this Pod (chicken-and-egg problem)
- be resolvable externally
- match the advertised name with the initial cluster
- this _probably_ isn't necessary if you use the Discovery URL method.
- We can't assign a clusterIP to the `Service` because if we do, the `PetSet`
unit names (e.g. etcd-0.etcd.default.svc.cluster.local) do not get created,
though the service does.
- We can't create a _separate_ service for clients with a clusterIP because
something apparently gets confused or crossed, and the `PetSet` unit names
don't get defined, either.
