we'll need to use helm to run install and test on integration agents to verify production images
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Pipeline: setup minikube in CI | operations/puppet | production | +59 -1 |
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 | 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 | • dduvall | T188934 install helm on integration agents | |||
Invalid | None | T190589 Packaged helm points to non-existent tiller |
Event Timeline
Comment Actions
We should be sure to add a necessary workaround to integration puppet for {T190589: Packaged helm points to non-existent tiller}.
Comment Actions
Change 428010 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[operations/puppet@production] Pipeline: setup minikube in CI
Comment Actions
@dduvall effectively solved this with https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/421973/
In the future, the only place where helm will be useful is on contint1001, which is currently assigned the profile::kubernetes::deployment_server, which takes care of helm for us.
Comment Actions
Change 428010 abandoned by Thcipriani:
Pipeline: setup minikube in CI
Reason:
No longer needed