search

SUSE / cap

Apache License 2.0
2 stars 1 forks source link

Provide no-op on deploy-k8s job when caasp4, for now #60

Closed viccuad closed 3 years ago

viccuad commented 3 years ago

CaaSP4 clusters are currently pets: we create them out of the pipeline, be it in ECP (we need to build a skuba image, and configure dind for concourse) or be it KVM (not added to catapult yet).

Hence, for caasp4 clusters, we need to not run deploy-k8s job.

Sadly, the pipeline definitions don't have a simple way to disable one job for 1 backend only.

We could deploy additional {cap-pre-release,cap-release,cap-release-upgrades,…}-caasp4.yaml pipelines, but it's messy. Or we could change the gomplate templating, for which we don't have time now.

Hence, make deploy-k8s do nothing when caasp4, for now.

viccuad commented 3 years ago

From feedback and after talking with Sebi, this is not going to work.

The deploy-k8s has a put to the pool, which we cannot satisfy on caasp, as we aren't creating the cluster. And we don't have a get in deploy-k8s either, so there's no way to shortcircuit with a no-op as done here.