-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docs for overview #4655
Update docs for overview #4655
Conversation
Signed-off-by: Yoshiki Fujikane <[email protected]>
b77eb7a
to
bcd687b
Compare
- Insights show metrics like lead time, deployment frequency, MTTR and change failure rate to measure delivery performance | ||
- Designed to manage thousands of cross-platform applications in multi-cloud for company scale but also work well for small projects | ||
|
||
## Characteristics in detail |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Characteristics in detail | |
## PipeCD's characteristics in detail |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4655 +/- ##
==========================================
+ Coverage 30.00% 30.81% +0.81%
==========================================
Files 221 221
Lines 25955 25941 -14
==========================================
+ Hits 7787 7995 +208
+ Misses 17519 17295 -224
- Partials 649 651 +2 ☔ View full report in Codecov by Sentry. |
@@ -49,3 +49,12 @@ Yes, you can use PipeCD for both mesh (Istio, SMI) applications and non-mesh app | |||
### 6. What should I do if I lost my Piped key? | |||
|
|||
You can create a new Piped key. Go to the `Piped` tab at `Settings` page, and click the vertical ellipsis of the Piped that you would like to create the new Piped key. Don't forget deleting the old Key, too. | |||
|
|||
### 7. What is the strong point if PipeCD is used only for k8s? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### 7. What is the strong point if PipeCD is used only for k8s? | |
### 7. What is the strong point if PipeCD is used only for Kubernetes? |
- easy to install and upgrade the tools, you just choose desired version on WebUI | ||
- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- easy to install and upgrade the tools, you just choose desired version on WebUI | |
- | |
- Simple interface, easy to understand no extra CRD required | |
- Easy to install, upgrade, and manage (both the ControlPlane and the agent Piped) | |
- Not strict depend on any Kubernetes API, not being part of issues for your Kubernetes cluster versioning upgrade | |
- Easy to interact with any CI; Plan preview feature gives you an early look at what will be changed in your cluster even before manifests update | |
- Insights show metrics like lead time, deployment frequency, MTTR, and change failure rate to measure delivery performance |
Signed-off-by: Yoshiki Fujikane <[email protected]>
4b2f84d
to
f99ddf4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧨
* update overview Signed-off-by: Yoshiki Fujikane <[email protected]> * Fix docs Signed-off-by: Yoshiki Fujikane <[email protected]> --------- Signed-off-by: Yoshiki Fujikane <[email protected]>
* update overview Signed-off-by: Yoshiki Fujikane <[email protected]> * Fix docs Signed-off-by: Yoshiki Fujikane <[email protected]> --------- Signed-off-by: Yoshiki Fujikane <[email protected]>
* update overview Signed-off-by: Yoshiki Fujikane <[email protected]> * Fix docs Signed-off-by: Yoshiki Fujikane <[email protected]> --------- Signed-off-by: Yoshiki Fujikane <[email protected]> Signed-off-by: 鈴木 優耀 <[email protected]>
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: