-
Notifications
You must be signed in to change notification settings - Fork 138
Conversation
Thanks @yanniszark @kkasravi comments? |
please help and take a look at condition types and reasons, I try to fit the new status into our new semantics. |
Will it be compatible with https://github.com/kubeflow/kubeflow/blob/v0.6-branch/bootstrap/config/kfctl_gcp_iap.0.6.2.yaml ? |
no, this is the new version. we will make kfctl to be backward compatible with v1alpha1 KfDef, tho. |
there is a merged doc on conditions and ApplicationStatusCondition |
@kkasravi I've updated the conditions part according to the link, could you take a second pass? |
thanks @gabrielwen |
@yanniszark will wait for your review. please approve this when you think it looks good. |
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.
@gabrielwen thanks for the PR!
I have left some comments below, please take a look and tell me what you think 😄
KfAvailable KfDefConditionType = "Available" | ||
|
||
// KfDegraded means functionality of Kubeflow is limited. | ||
KfDegraded KfDefConditionType = "Degraded" |
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.
What exactly does functionality is limited mean?
Can you give an example?
Is this meant to be used with the ApplyPluginsFailedReason reason?
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.
From the doc:
KfAvailable = true && KfDegraded = true
means KF is serving (central dashboard is accessible) but the services are limited. For example, we can use notebook but not pipelines.KfAvailable = false && KfDegraded = true
means KF is not serving and part/all of services are not serving as well.KfAvailable = true && KfDegraded = false
means KF is serving and all services are healthy.
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 believe this doc was mentioned by @kkasravi.
I don't have a problem with using the specific conditions, just wondering if they fit Kubeflow as well.
For example, I don't think we can detect a condition like "KF is serving but not all services are serving" in kfctl.
However, individual conditions do make sense.
In addition, the doc refers to a library that doesn't exist anymore (https://github.com/openshift-kni/operator-status).
I will update the design doc to refer to this doc.
@jlewi @kkasravi thoughts?
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 think we should follow the doc only if the conditions make sense in our use case.
I might also suggest holding off defining conditions until we are sure we need them; i.e. we are writing code to implement. I might suggest commenting out and explaining why or opening up an issue to define track what conditions we think we need.
We might want to hold off defining the conditions until we actually need them; i.e. are writing the code to implement them.
Adding conditions later doesn't break compatibility but removing ones could.
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.
ok, I removed most of conditions/reasons and only keep one or two placeholders that I think we definitely need them.
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.
@yanniszark @gabrielwen if KfDef becomes a CRD, should we define a structured schema
see
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.
@gabrielwen I have a few more comments on this, I think we're almost there.
KfAvailable KfDefConditionType = "Available" | ||
|
||
// KfDegraded means functionality of Kubeflow is limited. | ||
KfDegraded KfDefConditionType = "Degraded" |
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 believe this doc was mentioned by @kkasravi.
I don't have a problem with using the specific conditions, just wondering if they fit Kubeflow as well.
For example, I don't think we can detect a condition like "KF is serving but not all services are serving" in kfctl.
However, individual conditions do make sense.
In addition, the doc refers to a library that doesn't exist anymore (https://github.com/openshift-kni/operator-status).
I will update the design doc to refer to this doc.
@jlewi @kkasravi thoughts?
/hold cancel |
@yanniszark @kkasravi could I have lgtm from both of you? |
/lgtm |
/lgtm |
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 have a few more comments and this should be ready to go for me.
Great work!
@yanniszark done, could you take a final look? :) |
@gabrielwen thanks for all the great work. One last concern I had, which is worth mentioning now: AFAIK, we don't have a good story for providing secrets for securing applications. Are we confident that we'll be able to have a good story for this without needing a new version? @gabrielwen @jlewi that's all from my side, please remove the hold when you believe everything is ready. |
@yanniszark We can extend SecretSource if need be to allow people alternative methods of referencing secrets. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fix "replaces" property in 0.6.1 CSV
Update to latest 1.0.5 release
Bootstrapping KfDef for v1beta1.
Relates to kubeflow/kubeflow#4002
This change is