Descriptions for dividing subscription should be generated after related localizations was synced

[abstractmj]

Sometimes when the base arrives at the hub before the localization, the deployment in one member cluster may first expands from 0 to N, and then immediately shrinks to M;
0 < M < N

[dixudx]

clusternet/pkg/controllermanager/deployer/deployer.go

Lines 389 to 409 in 4330272

	newBaseName := fmt.Sprintf("%s-%s", sub.Namespace, sub.Name)
	base, err := deployer.syncBase(sub, baseTemplate, newBaseName)
	if err != nil {
	allErrs = append(allErrs, err)
	msg := fmt.Sprintf("Failed to sync Base %s: %v", klog.KObj(base), err)
	klog.ErrorDepth(5, msg)
	deployer.recorder.Event(sub, corev1.EventTypeWarning, "FailedSyncingBase", msg)
	// if sync base error, all base(new and old name format) need keep exist
	basesToBeDeleted.Delete(klog.KObj(baseTemplate).String())
	baseTemplate.Name = newBaseName
	basesToBeDeleted.Delete(klog.KObj(baseTemplate).String())
	continue
	}
	basesToBeDeleted.Delete(klog.KObj(base).String())
	// populate Localizations for dividing scheduling.
	err = deployer.populateLocalizations(sub, base, idx)
	if err != nil {
	allErrs = append(allErrs, err)
	klog.ErrorDepth(5, fmt.Sprintf("Failed to sync Localizations: %v", err))
	}

Normally Localization objects are created and updated after Base objects. Then controller Description will begin the rendering of descriptions objects.

Sometimes when the base arrives at the hub before the localization, the deployment in one member cluster may first expands from 0 to N, and then immediately shrinks to M;
0 < M < N

For newly created objects, there should only be from 0 to M.

But if a subscription is updated, then there will be an interim transition from N to M, just like what you said. In this case, it seems there is no way to avoid such transitions, unless we introduce a new flag to indicate the outdated localizations and hold the rendering of description objects.

[abstractmj]

"Normally Localization objects are created and updated after Base objects. Then controller Description will begin the rendering of descriptions objects."

But we cannot guarentee the creation order between Localization and Description, so description may be already applied in member cluster before Localization is handled by hub

[dixudx]

But we cannot guarentee the creation order between Localization and Description, so description may be already applied in member cluster before Localization is handled by hub

@abstractmj That's true. That's why I think we may introduce a new flag to indicate the outdated localizations and hold the rendering of description objects.