add rollout status in app api

[LiZhenCheng9527]

What type of PR is this?
/kind api-change

What this PR does / why we need it:
add rollout status in application api

[netlify]

✅ Deploy Preview for kurator-dev ready!

Name	Link
🔨 Latest commit	e6c73b4
🔍 Latest deploy log	https://app.netlify.com/sites/kurator-dev/deploys/65828ab0c2904500087e6856
😎 Deploy Preview	https://deploy-preview-520--kurator-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Xieql]

You have defined the RolloutStatus structure, but you haven't specified where it is used.

You might need to declare it in

kurator/pkg/apis/apps/v1alpha1/types.go

Lines 406 to 410 in 34ae6ed

	// ApplicationStatus defines the observed state of Application.
	type ApplicationStatus struct {
	SourceStatus *ApplicationSourceStatus `json:"sourceStatus,omitempty"`
	SyncStatus []*ApplicationSyncStatus `json:"syncStatus,omitempty"`
	}

[hzxuzhonghu]

This is different from fluxCD, which we create CR in management cluster,

But for rolling out we need to create CR in member clusters, i am not sure how can we watch the member cluster CR's status

[Xieql]

Yes, this approach differs from FluxCD.

It may not be feasible to directly monitor the status of Custom Resources (CRs) in member clusters.

Instead, we might need to continuously iterate over these CRs, checking them until they achieve the expected state.

see:

kurator/pkg/fleet-manager/backup/backup_controller.go

Lines 166 to 207 in 40eb58e

	// reconcileOneTimeBackupStatus updates the status of a one-time Backup object by checking the status of corresponding Velero backup resources in each target cluster.
	// It determines whether to requeue the reconciliation based on the completion status of all Velero backup resources.
	func (b *BackupManager) reconcileOneTimeBackupStatus(ctx context.Context, backup *backupapi.Backup, destinationClusters map[fleetmanager.ClusterKey]*fleetmanager.FleetCluster, statusMap map[string]*backupapi.BackupDetails) (ctrl.Result, error) {
	log := ctrl.LoggerFrom(ctx)
	// Loop through each target cluster to retrieve the status of Velero backup resources using the client associated with the respective target cluster.
	for clusterKey, clusterAccess := range destinationClusters {
	name := generateVeleroResourceName(clusterKey.Name, BackupKind, backup.Namespace, backup.Name)
	veleroBackup := &velerov1.Backup{}
	// Use the client of the target cluster to get the status of Velero backup resources
	err := getResourceFromClusterClient(ctx, name, VeleroNamespace, *clusterAccess, veleroBackup)
	if err != nil {
	log.Error(err, "failed to create velero backup instance for sync one time backup status")
	return ctrl.Result{}, err
	}
	key := fmt.Sprintf("%s-%s-%s", clusterKey.Name, clusterKey.Kind, veleroBackup.Name)
	if detail, exists := statusMap[key]; exists {
	// If a matching entry is found, update the existing BackupDetails object with the new status.
	detail.BackupStatusInCluster = &veleroBackup.Status
	} else {
	// If no matching entry is found, create a new BackupDetails object and append it to the backup's status details.
	currentBackupDetails := &backupapi.BackupDetails{
	ClusterName: clusterKey.Name,
	ClusterKind: clusterKey.Kind,
	BackupNameInCluster: veleroBackup.Name,
	BackupStatusInCluster: &veleroBackup.Status,
	}
	backup.Status.Details = append(backup.Status.Details, currentBackupDetails)
	}
	}
	// Determine whether to requeue the reconciliation based on the completion status of all Velero backup resources.
	// If all backups are complete, exit directly without requeuing.
	// Otherwise, requeue the reconciliation after a specified interval (StatusSyncInterval).
	if allBackupsCompleted(backup.Status) {
	return ctrl.Result{}, nil
	} else {
	return ctrl.Result{RequeueAfter: StatusSyncInterval}, nil
	}
	}

[hzxuzhonghu]

From my perspective this is MetricName

[LiZhenCheng9527]

@hzxuzhonghu

[hzxuzhonghu]

/lgtm

[kurator-bot]

[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:

• OWNERS [hzxuzhonghu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment