Skip to content
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

Clarify the meaning of the CRDs .status.conditions #640

Open
rgl opened this issue Apr 7, 2024 · 1 comment
Open

Clarify the meaning of the CRDs .status.conditions #640

rgl opened this issue Apr 7, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@rgl
Copy link

rgl commented Apr 7, 2024

Can you please clarify the meaning of the CRDs .status.conditions?

That would be especially useful for a newbie like me :-)

For example, at https://github.com/piraeusdatastore/piraeus-operator/blob/v2.5.0/docs/reference/linstorcluster.md#statusconditions, its not clear how to wait for a condition that means "How do I wait until the LinstorCluster is ready to use (i.e. I can create a persistent volume from it)?"

For me, its not clear whether these conditions are related, whether they progress (e.g. Configured -> Available > Applied), or if they can be set at the same time, IOW, maybe have some kind of state machine diagram?

It would also help to include an example on how to wait for a condition to be meet? For example:

kubectl wait LinstorCluster/linstorcluster --timeout=5m --for=condition=Applied
@WanzenBug
Copy link
Member

I guess the best way to wait for "everything" to be done is:

kubectl wait LinstorCluster/linstorcluster --timeout=5m --for=condition=Configured
kubectl wait LinstorSatellite --all --timeout=5m --for=condition=Configured

@WanzenBug WanzenBug added documentation Improvements or additions to documentation good first issue Good for newcomers labels Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants