skaffold is a command line tool that facilitates continuous development for Kubernetes applications. We should evaluate whether it can be used in local development for the purposes of the MediaWiki-Containers project.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| 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 | • mobrovac | T170456 FY2017/18 Program 6 - Outcome 2 - Objective 3: Integrated, container-based development environment | |||
| Resolved | • mobrovac | T183743 FY17/18 Q3 Program 6 Services Goal: Tools for managing services in minikube | |||
| Declined | None | T194024 Evaluate skaffold for local development |
Event Timeline
Comment Actions
Wouldn't Helm be appropriate here? This is what we're planning with the related tasks.
Comment Actions
Chad was right back then :) Looks like heml is the de-facto standard for us in the Release Pipeline program.
Being bold and declining.