This allows manifests to be deployed in either the normal Vagrant sandbox or Kind, using KubeVirt. There is also a README and some manifests to help deploying Tinkerbell in Kind even though it remains tricky.
Why is this needed
This is a step forward to standardize deployment in Kubernetes. While k8s-sandbox is useful to test real-life scenarios, https://github.com/detiber/tink/tree/kindDev is great for development. By merging the two repositories, the idea is to make development and "prod" environments as similar as possible.
How Has This Been Tested?
vagrant_test.go ran successfully and also validated manually. It also ran in Kind by modifying .env file as documented.
How are existing users impacted? What migration steps/scripts do we need?
n/a
Checklist:
I have:
[x] updated the documentation and/or roadmap (if required)
mrchrd
commented
3 years ago
Description
This allows manifests to be deployed in either the normal Vagrant sandbox or Kind, using KubeVirt. There is also a README and some manifests to help deploying Tinkerbell in Kind even though it remains tricky.
Why is this needed
This is a step forward to standardize deployment in Kubernetes. While k8s-sandbox is useful to test real-life scenarios, https://github.com/detiber/tink/tree/kindDev is great for development. By merging the two repositories, the idea is to make development and "prod" environments as similar as possible.
How Has This Been Tested?
vagrant_test.go ran successfully and also validated manually. It also ran in Kind by modifying .env file as documented.
How are existing users impacted? What migration steps/scripts do we need?
n/a
Checklist:
I have: