Add tutorial for local PipeCD setup using Kind#6539
Open
Lochipi wants to merge 2 commits intopipe-cd:masterfrom
Open
Add tutorial for local PipeCD setup using Kind#6539Lochipi wants to merge 2 commits intopipe-cd:masterfrom
Lochipi wants to merge 2 commits intopipe-cd:masterfrom
Conversation
eeshaanSA
requested changes
Feb 23, 2026
eeshaanSA
requested changes
Feb 24, 2026
Contributor
There was a problem hiding this comment.
We need weight field. Just a proper number.
Author
There was a problem hiding this comment.
Hi, thanks for the review. I had 992 before. Do you want me to set it back to 992? or keep the new lower number?
Also, what rule should I follow for next posts:
match by date order?
keep weights unique?
I can see inconsistencies in numbers, and I'm not yet sure how this works.
Contributor
|
Let's match the weight date wise. Or you can just make sure this blog stays
at the top.
…On Tue, 24 Feb 2026 at 16:40, Cornelius Emase ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
On docs/content/en/blog/install-pipecd-locally-using-kind.md
<#6539 (comment)>:
Hi, thanks for the review. I had 992 before. Do you want me to set it back
to 992? or keep the new lower number?
Also, what rule should I follow for next posts:
match by date order?
keep weights unique?
I can see inconsistencies in numbers, and I'm not yet sure how this works.
—
Reply to this email directly, view it on GitHub
<#6539 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYADV4XLOIKYD2XREEQ33CT4NQWRNAVCNFSM6AAAAACV4LJBX6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTQNBWHEZTINBSGQ>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
Lochipi
force-pushed
the
docs/blog-kind-local-install-guide
branch
from
ae8ce11 to
d7e4f61
Compare
Signed-off-by: Cornelius Emase <corneliuslochipi@gmail.com>
Signed-off-by: Cornelius Emase <corneliuslochipi@gmail.com>
Lochipi
force-pushed
the
docs/blog-kind-local-install-guide
branch
from
d7e4f61 to
4ddc3c4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does:
Adds a new blog post that explains how to install and run PipeCD locally using Kind (Kubernetes in Docker).
Why we need it:
Users want a simple way to try PipeCD on their own machines before using it in production. This guide helps them get started quickly without needing cloud resources.
Which issue(s) this PR fixes:
Fixes #6524
Does this PR introduce a user-facing change?:
Yes
How are users affected by this change: Users now have a step-by-step guide to run PipeCD locally. This helps them learn and test PipeCD before moving to production.
Is this breaking change: No
How to migrate (if breaking change): N/A