-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add README with CLI usage descriptions #20
Conversation
@@ -0,0 +1,110 @@ | |||
# Scalar Admin k8s | |||
|
|||
## Usage of the CLI tool |
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.
This is an output of the scalar-admin-k8s
CLI. I think there is no document that describes each flag of scalar-admin-k8s
. This is the main purpose of this PR.
This section describes the scalar-admin-k8s
options and I can link to this document in the document of Helm Chart to explain the flags of scalar-admin-k8s
.
README.md
Outdated
zone ID is case sensitive. Etc/UTC by default. | ||
``` | ||
|
||
## Run the CLI tool on a Kubernetes environment |
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.
This section explains how to run the scalar-admin-k8s
CLI tool manually.
However, I think there are almost no users to use this way.
We assume that users use Helm Chart instead of that.
README.md
Outdated
- <TIMEZONE> | ||
``` | ||
|
||
## Run the CLI tool on a Kubernetes environment by using Helm Chart |
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.
After I release the Helm Chart, I will update this section (add a link to the document of Helm Chart) in the future.
We assume that almost all users use this way for backup operations.
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.
LGTM! I left one minor comment. Please take a look.
-n, --namespace=<namespace> | ||
Namespace that Scalar products you want to pause | ||
are deployed. `default` by default. | ||
-r, --release-name=<helmReleaseName> |
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.
To be clear, only -r
is required, correct? If so, I think it would be helpful to note that this parameter is required in the parameter description here.
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.
To be clear, only
-r
is required, correct?
Yes. You are right.
If so, I think it would be helpful to note that this parameter is required in the parameter description here.
I see. I agree with adding a note.
I will do it in another PR.
Thank you for your suggestion!
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.
LGTM.
Thank you!
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.
I've added some comments and suggestions. PTAL!
README.md
Outdated
|
||
## Run the CLI tool on a Kubernetes environment | ||
|
||
The `scalar-admin-k8s` CLI tool executes Kubernetes APIs in its internal processes. To run those Kubernetes APIs, you must run the `scalar-admin-k8s` CLI tool as a pod on the Kubernetes environment and you must: |
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.
Depending on what we call the product (as mentioned in my previous comment), the product mentions in this paragraph might need to be updated.
The `scalar-admin-k8s` CLI tool executes Kubernetes APIs in its internal processes. To run those Kubernetes APIs, you must run the `scalar-admin-k8s` CLI tool as a pod on the Kubernetes environment and you must: | |
The `scalar-admin-k8s` CLI tool executes Kubernetes APIs in its internal processes. To run those Kubernetes APIs, you must run the `scalar-admin-k8s` CLI tool as a pod on the Kubernetes environment and then do the following: |
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.
@josh-wong
Thank you for your suggestion!
In practice, the content of this section is a steps
to deploy Scalar Admin for Kubernetes CLI on the Kubernetes environment. In other words, run CLI tool as a pod
is included in the steps. So, I feel and then
is a bit not fit in this section.
So, how about the following sentence?
The `scalar-admin-k8s` CLI tool executes Kubernetes APIs in its internal processes. To run those Kubernetes APIs, you must run the `scalar-admin-k8s` CLI tool as a pod on the Kubernetes environment and you must: | |
The `scalar-admin-for-kubernetes` CLI tool executes Kubernetes APIs in its internal processes. To run those Kubernetes APIs, you must run the `scalar-admin-for-kubernetes` CLI tool as a pod on the Kubernetes environment by following to below steps. |
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.
@kota2and3kan Thank you for clarifying that! I assumed the steps were separate from the you must run
part since we use and
to introduce the steps.
In this case, let's use the following:
The `scalar-admin-k8s` CLI tool executes Kubernetes APIs in its internal processes. To run those Kubernetes APIs, you must run the `scalar-admin-k8s` CLI tool as a pod on the Kubernetes environment and you must: | |
The `scalar-admin-for-kubernetes` CLI tool executes Kubernetes APIs in its internal processes. To run those Kubernetes APIs, you must run the `scalar-admin-for-kubernetes` CLI tool as a pod on the Kubernetes environment by following the steps below: |
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.
@josh-wong
Thank you for your suggestion!
I applied it in 8d5d2a4 .
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.
Overall, looking good!
Left one suggestion. PTAL!
@@ -0,0 +1,110 @@ | |||
# Scalar Admin 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.
Can you add a few sentences describing what this is?
I think it's helpful even for internal developers.
Something like the following.
scalar-admin-k8s is a tool that creates a paused state for Scalar products (e.g., ScalarDB and ScalarDL) in a Kubernetes environment. We can use such a paused state to take backups easily and consistently across multiple diverse databases.
(This might need to be checked by @josh-wong if it is used.)
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.
I added such an explanation in 71c433e.
@josh-wong
Could you please also check this new sentence? Thank you!
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.
I was unable to suggest changes to the sentence in a reply to this message, so I added a new comment with my suggestion to the updated sentence.
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.
I've left a few minor suggestions. Other than that, LGTM! Thank you🙇🏻♂️
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.
LGTM! Thank you!
Co-authored-by: Josh Wong <[email protected]>
Co-authored-by: Josh Wong <[email protected]>
Co-authored-by: Josh Wong <[email protected]>
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.
LGTM! Thank you!
Description
This PR adds a
README
. At this time, it includes descriptions about the CLI tool only.This is because I need the document of the CLI tool itself to create a new document on the Helm Chart side.
I think we can add descriptions about the Java library if we need it in the future.
Related issues and/or PRs
N/A
Changes made
Add
README
.Checklist
Additional notes (optional)
At the moment, I think we do NOT need to add this
README
to the document side.This is because we assume that users use Helm Chart to run the Scalar Admin k8s instead of running the CLI tool directly.
In the future, I will create the document
how to run Scalar Admin k8s by using Helm Chart
in the Helm Chart repository and the documenthow to perform the backup operation by using Scalar Admin k8s
in thescalar-kubernetes
repository.These two documents can help users to run the backup operation. So, I think these documents should be added to the doc site in the future instead of this
README
.