etcd-io / etcd-io/auger

Schema pull at runtime

Open
#33 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
121
Forks
37
Avg merge
9d 9h
Merged PRs (30d)
7

Description

It seems that we have to support a fairly big matrix of `etcd versions x kubernetes versions x(+- crds installed)`.

Looking into autogen in #2 and James's effort in #32, which is a great start into getting this project updated - is this a viable path forward?

All the API descriptors are either available from Github or directly from the apiserver and we _could_ also pull them on demand from there, given the currently installed etcd and k8s version.

Another important addition to k8s since the project start are CRDs, how would we get their schema if not from apiserver directly?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.