Skip to content

Draft: Fix env specific only/except:kubernetes:active and CI_KUBERNETES_ACTIVE

Hordur Freyr Yngvason requested to merge fix-kubernetes-active-scoping into master

What does this MR do and why?

This is a proposed fix for a long standing bug where a *-scoped cluster was required for only/except:kubernetes:active and the variable CI_KUBERNETES_ACTIVE.

Scoped variables are evaluated with the expanded environment scope and passed to rules. This includes any deployment variables that do not depend on a materialized namespace and service account token.

So we can add an environment-specific CI_KUBERNETES_ACTIVE deployment variable and then also use that variable for only/except:kubernetes:active.

Because CI_KUBERNETES_ACTIVE is already also an unscoped pipeline-level variable, the environment-specific variable must supplement it to avoid breaking dependencies workflow:rules using CI_KUBERNETES_ACTIVE.

See #20351 (closed)

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports