[K8s Plugin] Implement K8S_BASELINE_ROLLOUT#5870
Conversation
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
…t stage Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
…ervice properties in baseline tests Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
…ce YAML files in baseline rollout tests Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5870 +/- ##
==========================================
+ Coverage 27.85% 27.89% +0.04%
==========================================
Files 519 519
Lines 55793 55900 +107
==========================================
+ Hits 15539 15594 +55
- Misses 39070 39108 +38
- Partials 1184 1198 +14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…d NestedSlice calls for service spec Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
|
|
||
| // addVariantLabelsAndAnnotations adds the variant label and annotation to the given manifests. | ||
| // This also adds the resource key to the manifest. | ||
| // This is because the resource key differs between variants. |
There was a problem hiding this comment.
[ask] Can you show me an example of the expected case of this comment?
There was a problem hiding this comment.
Thank you.
I added it as a comment because it's better to have it in this comment.
https://github.com/pipe-cd/pipecd/pull/5870/files/1656704e0390b8235ee6d2ec7391bbd456252886..ff25ca493ff82d1b5840bfb686a950ca596494e6
There was a problem hiding this comment.
Thank you. I understood that.
IMO, it's better to fix the resource key annotation when generating variant manifests (insidegenerateBaselineManifests) to separate the responsibility for each function. WDYT?
There was a problem hiding this comment.
I agree with you; it's clear to do this when generating variant manifests.
I'll change the code.
| variantLabel: variant, | ||
| provider.LabelResourceKey: m.Key().String(), |
There was a problem hiding this comment.
[nit] add the same comment for k8s plugins' fixes
There was a problem hiding this comment.
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
t-kikuc
left a comment
There was a problem hiding this comment.
Let's merge after separating the SDK (and solving conflicts)
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
|
Solved the conflicts and import error |
What this PR does:
Why we need it:
To support k8s pipeline sync in the plugin
Which issue(s) this PR fixes:
Part of #5764
Does this PR introduce a user-facing change?: