Package up minikube to create an isolated k8s context in which release pipeline containers can be run to verify their basic functionality (i.e., service responds, etc.)
|Resolved||None||T170453 FY2017/18 Program 6: Streamlined Service delivery|
|Invalid||None||T170480 FY2017/18 Program 6 - Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment.|
|Invalid||None||T170481 FY2017/18 Program 6 - Outcome 2 - Objective 2: Set up a continuous integration and deployment pipeline|
|Resolved||None||T157469 Mathoid CI Container Build|
|Resolved||dduvall||T183165 Verify functionality of the 'production' image in the context of an isolated k8s deployment|
|Resolved||thcipriani||T184457 Installation method for Minikube on CI for k8s testing|
I've made a flattened clone of minikube at https://gerrit.wikimedia.org/r/#/admin/projects/operations/debs/minikube and added all the debian control files to that tree: https://gerrit.wikimedia.org/r/plugins/gitiles/operations/debs/minikube/+/master/debian/
I've been able to get a working minikube deb setup on a few VMs from this (although it requires golang 1.9 to build it's not linked against anything that isn't available in stretch, seemingly). @akosiaris since you've been doing a lot of the packaging for k8s and k8s-adjacent things, could I get you to take a look at building/uploading this to the thirdparty/ci component?
Please let me know if there are problems.
Aside from having to tag the release locally with v0.25.0 so that gbp could generate the source and using buster to build this, everything else worked out fine. Being go it even worked on jessie so I 've uploaded it already to thirdparty/ci. I 'll resolve this, feel free to reopen