Skip to content

[Multi_K8s-Plugin] rename stages to avoid conflicts with kubernetes plugin#6880

Merged
Warashi merged 2 commits into
pipe-cd:masterfrom
mohammedfirdouss:feat/multicluster-stage-rename
May 30, 2026
Merged

[Multi_K8s-Plugin] rename stages to avoid conflicts with kubernetes plugin#6880
Warashi merged 2 commits into
pipe-cd:masterfrom
mohammedfirdouss:feat/multicluster-stage-rename

Conversation

@mohammedfirdouss
Copy link
Copy Markdown
Contributor

What this PR does: Renames the Kubernetes multicluster plugin stage names to include a MULTI_ prefix, avoiding collisions with the regular Kubernetes plugin stage names.

Why we need it: A Piped instance cannot have two plugins registering the same stage name. The multicluster plugin previously used identical names to the Kubernetes plugin (K8S_PRIMARY_ROLLOUT, K8S_CANARY_ROLLOUT, etc.), which would cause routing conflicts when both plugins are loaded.

The following stages are renamed:

  • K8S_PRIMARY_ROLLOUTK8S_MULTI_PRIMARY_ROLLOUT
  • K8S_CANARY_ROLLOUTK8S_MULTI_CANARY_ROLLOUT
  • K8S_CANARY_CLEANK8S_MULTI_CANARY_CLEAN
  • K8S_BASELINE_ROLLOUTK8S_MULTI_BASELINE_ROLLOUT
  • K8S_BASELINE_CLEANK8S_MULTI_BASELINE_CLEAN
  • K8S_TRAFFIC_ROUTINGK8S_MULTI_TRAFFIC_ROUTING

Which issue(s) this PR fixes: Fixes #

Does this PR introduce a user-facing change?:

  • How are users affected by this change: Users need to update their app.pipecd.yaml pipeline stage names to use the new K8S_MULTI_* prefixed names.
  • Is this breaking change: Yes
  • How to migrate (if breaking change): Replace the old stage names with the new prefixed equivalents in all app.pipecd.yaml files that use the Kubernetes multicluster plugin.

…lugin

Signed-off-by: Mohammed Firdous <124298708+mohammedfirdouss@users.noreply.github.com>
@mohammedfirdouss mohammedfirdouss force-pushed the feat/multicluster-stage-rename branch from 3e53228 to 214023f Compare May 29, 2026 23:19
@mohammedfirdouss
Copy link
Copy Markdown
Contributor Author

@Warashi check here, thanks.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 29, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 29.36%. Comparing base (b173385) to head (ed33f3f).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #6880      +/-   ##
==========================================
- Coverage   29.37%   29.36%   -0.01%     
==========================================
  Files         601      601              
  Lines       64282    64282              
==========================================
- Hits        18883    18879       -4     
- Misses      43931    43934       +3     
- Partials     1468     1469       +1     
Flag Coverage Δ
. 23.14% <ø> (ø)
.-pkg-app-pipedv1-plugin-analysis 32.43% <ø> (ø)
.-pkg-app-pipedv1-plugin-ecs 31.74% <ø> (ø)
.-pkg-app-pipedv1-plugin-kubernetes 58.37% <ø> (ø)
.-pkg-app-pipedv1-plugin-kubernetes_multicluster 59.66% <ø> (ø)
.-pkg-app-pipedv1-plugin-scriptrun 54.83% <ø> (ø)
.-pkg-app-pipedv1-plugin-terraform 37.95% <ø> (ø)
.-pkg-app-pipedv1-plugin-wait 33.04% <ø> (ø)
.-pkg-app-pipedv1-plugin-waitapproval 52.71% <ø> (ø)
.-pkg-plugin-sdk 50.14% <ø> (-0.20%) ⬇️
.-tool-actions-gh-release 19.23% <ø> (ø)
.-tool-actions-plan-preview 25.51% <ø> (ø)
.-tool-codegen-protoc-gen-auth 0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Member

@Warashi Warashi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Thank you

@Warashi Warashi merged commit 3303442 into pipe-cd:master May 30, 2026
61 of 62 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

Thank you for contributing to PipeCD! The changes in this pull request will be part of the upcoming release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants