-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create kube-timer-instruction.md #2
base: master
Are you sure you want to change the base?
Conversation
Can we replace the content in README.md instead of creating a new doc? |
## Parameters of kube-timer | ||
| Parameter | Description | | ||
| --------- | ------------- | | ||
| -f | The yaml file for resources provision | |
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 we specify which ones are required flags?
You could run the below command in the terminal to install kube-timer tool. | ||
|
||
```shell | ||
go install github.com/nilo19/kube-timer |
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 we append @latest
?
|
||
This articles provides the instructions about how get the provision/deletion time of kubernetes resources. It contains the installtion steps, description of parameters and samples outputs. | ||
|
||
## How to install kube-timer |
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.
Installation
|
||
# Use kube-timer to get the provision/deletion time of kubernetes resources | ||
|
||
This articles provides the instructions about how get the provision/deletion time of kubernetes resources. It contains the installtion steps, description of parameters and samples outputs. |
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 we make it: "kube-time is a xxxxx"
| -c | The number of resource | | ||
| -a | Create all the resources together and wait for the previous resouces to be ready. The time of single resource creation would contain waiting in queue time. Without this parameter, the resources are created one by one; the next resource will only be created once the previous one is ready.| | ||
| -d | Delete the resource | | ||
| -n | Name of the resource to be leleted | | ||
| -D | Delete all the resources together | | ||
| --started-event-reason | The reason of event. It can be used as the start time of provision/deletion | | ||
| --finished-event-reason | The reason of event. It can be used as the end time of provision/deletion | | ||
| --namespace | The namespace of resources | |
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.
Currently, these only work for service.
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.
LB-typed service in particular.
|
||
#### Do not contain waiting-in-queue time | ||
|
||
As we do not specify `-a`, all the services will be created one by one. The next service is only be created once the previous one is ready. |
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 the behavior of the cloud provider azure, we shouldn't assume all providers work like that.
2. Sample YAML definition: | ||
|
||
```yml | ||
kind: Service |
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 we prettify the yaml by removing redundant comments?
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 we address that the generateName is needed?
``` | ||
|
||
4.Sample output: | ||
![image](https://user-images.githubusercontent.com/45681473/177050104-b3a7fa1e-08ad-4811-a1b2-fc6c83e15101.png) |
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.
We can show the output by text.
![image](https://user-images.githubusercontent.com/45681473/177050104-b3a7fa1e-08ad-4811-a1b2-fc6c83e15101.png) | ||
|
||
|
||
#### Contains waiting-in-queue time |
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.
Again, we need to put it clear that this behavior varies from each cloud provider.
No description provided.