Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] hydroplane: add a runtime backend for Kubernetes IN Docker (kind) #11

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

MadhavJivrajani
Copy link

@MadhavJivrajani MadhavJivrajani commented Nov 16, 2023

This PR adds a runtime backend for kind, which is a fully
conformant Kubernetes distribution created and maintained by the
Kubernetes community: https://kind.sigs.k8s.io/

Having a kind backend helps users test Kubernetes deployments via
Hydro, but locally and in a lightweight manner. kind is also used
in running the CI for the Kubernetes project, which makes it suitable
for writing and running more sophisticated e2e tests for Kubernetes
on hydroplane.

This commit introduced a configuration file for the kind runtime and
adapts the Kubernetes util functions to work with it while not breaking
existing compatibility.

There are some pitfalls to how things are done in the present state
of the commit, primarily how node port mappings are handled. But
considering this backend would be used primarily for testing purposes,
having a less than ideal configuration mechanism might be within the
appetite of complexity we are willing to take on.

TODO:
Add docs

This commit adds a runtime backend for kind, which is a fully
conformant Kubernetes distribution created and maintainer by the
kubernetes community: https://kind.sigs.k8s.io/

Having a kind backend helps users test Kubernetes deployment via
Hydro, but locally and in a lightweight manner. kind is also used
in running the CI for the Kubernetes project, which makes it suitable
for writing and running more sophisticated e2e tests for Kubernetes
on hydroplane.

This commit introduced a configuration file for the kind runtime and
adapts the Kubernetes util functions to work with it while not breaking
existing compatibility.

There are some pitfalls to how things are done in the present state
of the commit, primararily how node port mappings are handled. But
considering this backend would be used primarily for testing purposes,
having a less than ideal configuration mechanism might be within the
appetite of complexity we are willing to take on.

Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant