openshift / ci-operator

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Avoid duplicating common logic in Openshift templates

0xmichalis opened this issue · comments

We need a way to reuse a single Openshift template which provides us a fresh cluster installed on Azure. We want to be able to execute actions before and after the cluster is installed. Examples for running before include building a node image that the install can use. Examples for running logic after include running all sorts of e2e tests or upgrades.

Strawman implementation: ci-operator reads a golang template and based on parameters provided into its env, it generates the actual Openshift template to use. Templates all the way down.

Another alternative was brought up by @stevekuznetsov in one of the latter ci meetings. IIUC, he alluded to adding cluster provisioning logic in the ci-operator so we could avoid using templates.

Thoughts?

@bbguimaraes @droslean @petr-muller @smarterclayton @stevekuznetsov

@openshift/sig-azure fyi

@stevekuznetsov: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.