-
Notifications
You must be signed in to change notification settings - Fork 37
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
Feat: Single cluster deployment application #667
Conversation
✅ Deploy Preview for kurator-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
pkg/apis/apps/v1alpha1/types.go
Outdated
@@ -47,6 +47,7 @@ type ApplicationSpec struct { | |||
SyncPolicies []*ApplicationSyncPolicy `json:"syncPolicies"` | |||
// Destination defines the destination clusters where the artifacts will be synced. | |||
// It can be overriden by the syncPolicies' destination. | |||
// And if both the current field and syncPolicies' destination are empty, the application will be deployed directly in the current cluster. |
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.
To be more accurate, current cluster should be the the cluster where kurator resides
log.Info("fleet does not exist", "fleet", fleetKey) | ||
return ctrl.Result{RequeueAfter: fleetmanager.RequeueAfter}, nil | ||
var fleet *fleetapi.Fleet | ||
if fleetKey.Name != "" { |
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.
when this can be empty
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.
return a.reconcile(ctx, app, fleet) |
fleet is used here
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
Can you add an e2e in the following pr
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hzxuzhonghu 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 |
Signed-off-by: yeyeye2333 <3229833855@qq.com>
Signed-off-by: yeyeye2333 <3229833855@qq.com>
Signed-off-by: yeyeye2333 <3229833855@qq.com>
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Allow setting the application's destination to a cluster, reducing the operational steps and enabling users to seamlessly use Kurator in a single-cluster, thereby increasing Kurator's flexibility.
Which issue(s) this PR fixes:
Fixes #653
Does this PR introduce a user-facing change?:
The application can be directly deployed to the current host cluster through the following configuration