-
Notifications
You must be signed in to change notification settings - Fork 22
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
Support apply PVC template changes to StatefulSet #412
Conversation
10b6f7d
to
09625b8
Compare
09625b8
to
8ce8915
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.
LGTM
message: "Validation failed: ..." | ||
``` | ||
|
||
Set the `VolumeResized` condition's status to `True` if the PVC expansion was successful. |
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.
That fine with me.
Could you also export this status as a metric?
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 see, I came up with two options, which would you prefer?
- Count metric,
moco_pvc_expansion_failed
- Count is incremented if PVC resizing fails
- Gauge metric,
moco_pvc_expansion_status{states="True/False"}
- Aggregate the number of objects from the list of MySQLCluster's that currently exist with that status
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.
Could you export this metrics for each MySQLCluster?
And also use the prefix of moco_cluster_
as with other metrics.
https://github.com/cybozu-go/moco/blob/main/docs/metrics.md#mysql-clusters
How about use the following format?
Count metircs: moco_cluster_volume_resized_total{status="True/False", name="mycluster", namespace="mynamesapce"}
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.
@masa213f
As I told you elsewhere, moco-controller should re-create StatefulSet not only when the storage size is changed, but also when metadata (labels / annotations) is changed. Considering that, the metric name containing volume_resized
is not appropriate.
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.
@d-kuro Have you heard about that?
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.
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 updated the docs to reflect the comments 🙏 :
e63a1d5
Signed-off-by: d-kuro <[email protected]>
…ding volume Signed-off-by: d-kuro <[email protected]>
e934847
to
11475fa
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.
LGTM. Great job! Thank you.
Hello, Do you have any release date which will include this feature please ? |
@donch |
Sorry, preparation of release has been delayed. I will release it next week. :( |
refs: #265
Add design documentation for moco-controller to support volume size expansion