-
Notifications
You must be signed in to change notification settings - Fork 407
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
Proposal: YurtAppDaemon #422
Proposal: YurtAppDaemon #422
Conversation
@kadisi: GitHub didn't allow me to assign the following users: your_reviewer. Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind feature |
/kind documentation |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kadisi 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 |
@kadisi Based on the proposal, An idea comes out that combine |
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.
@kadisi , as wenjun mentioned about the united-service feature request on last community meeting, the uniteddaemonset workload template will add ServiceTemplate support in future, right?
for daemonset, another question. now UnitedDeployment supports StatefulSet and Deployment. if DaemonSet (one pod per node in nodepool) should be supported also? i think it has its scenarios. if the above thought is reasonable, then there is something subtle about naming here: daemonset means one deployment per nodepool (pool level daemonset), or one pod per node (node level daemonset)? sounds UnitedDaemonSet can have some stress on nodepool level, and thus are at the same level as UnitedDeployment. |
I can see the difference between UnitedDeamonset and UnitedDeployment as the former can automatically deploy workload when nodepool is created. The benefit is that we can could avoid manually changing UnitedDeployment had it been used for the same purpose. The naming maybe misleading, how about NodePoolDaemonSet? |
@rambohe-ch This is not necessary, UnitedDeployment is not strongly associated with NodePool。If you delete a Pool in UnitedDeployment,sub Deployments/Statefulset will be automatically deleted |
@gnunu |
@Fei-Guo good idea |
5a2210d
to
6430a50
Compare
Signed-off-by: bingyu.zj <bingyu.zj@alibaba-inc.com>
6430a50
to
6d4f1f8
Compare
|
||
- What is the plan for implementing this feature? | ||
|
||
Provide yurtunit-manager operator to YurtAppDaemon CRD |
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.
yurtunit-manager --> yurt-app-manager?
## Implementation History | ||
|
||
+ [ ] : YurtAppDaemon api crd | ||
+ [ ] : yurtunit-manager YurtAppDaemon controller |
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.
yurtunit-manager --> yurt-app-manager?
WorkLoadProvisioned YurtAppDaemonConditionType = "WorkLoadProvisioned" | ||
// WorkLoadUpdated means all the workload are updated. | ||
WorkLoadUpdated YurtAppDaemonConditionType = "WorkLoadUpdated" | ||
// WorkLoadFailure is added to a UnitedDeployment when one of its workload has failure during its own reconciling. |
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.
UnitedDeployment --> YurtAppManager?
// +kubebuilder:printcolumn:name="WorkloadTemplate",type="string",JSONPath=".status.templateType",description="The WorkloadTemplate Type." | ||
// +kubebuilder:printcolumn:name="AGE",type="date",JSONPath=".metadata.creationTimestamp",description="CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC." | ||
|
||
// YurtAppDaemon is the Schema for the uniteddeployments API |
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.
uniteddeployment --> yurtappdaemons?
Items []YurtAppDaemon `json:"items"` | ||
} | ||
|
||
// WorkloadTemplate defines the pool template under the UnitedDeployment. |
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.
UnitedDeployment --> YurtAppDaemon?
1e4cedd
to
b5bdbbf
Compare
How about adding patch feature to YurtAppDaemon, just like we did in YurtAppSet. |
Signed-off-by: bingyu.zj <bingyu.zj@alibaba-inc.com>
b5bdbbf
to
1616206
Compare
@DrmagicE I think we'd better implement general YurtAppDaemon at first. and after that we can discuss whether add patch feature or not based on requirements from end users. |
@rambohe-ch OK, It is reasonable. |
/lgtm |
* Proposal: UnitedDaemonSet Signed-off-by: bingyu.zj <bingyu.zj@alibaba-inc.com> * change uniteddaemonset to yurtappdaemon Signed-off-by: bingyu.zj <bingyu.zj@alibaba-inc.com> Co-authored-by: bingyu.zj <bingyu.zj@alibaba-inc.com>
Signed-off-by: zhenggu1 <zhengguang.zhang@intel.com>
* Proposal: UnitedDaemonSet Signed-off-by: bingyu.zj <bingyu.zj@alibaba-inc.com> * change uniteddaemonset to yurtappdaemon Signed-off-by: bingyu.zj <bingyu.zj@alibaba-inc.com> Co-authored-by: bingyu.zj <bingyu.zj@alibaba-inc.com>
Signed-off-by: bingyu.zj bingyu.zj@alibaba-inc.com
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
other Note