Federated workloads' status is not updated with availableReplicas/readyReplicas

[pacoxu]

What would you like to be added:

Current status of FederatedDeployment

  status:
    clusters:
    - name: paco81
    - name: cluster0
    conditions:
    - lastTransitionTime: "2020-06-30T02:23:45Z"
      lastUpdateTime: "2020-06-30T02:42:22Z"
      status: "True"
      type: Propagation
    observedGeneration: 2

Deployment status

  status:
    availableReplicas: 1
    conditions:
    - lastTransitionTime: "2020-06-28T08:54:27Z"
      lastUpdateTime: "2020-06-28T08:54:36Z"
      message: ReplicaSet "python2-5qnzb-deployment-67ddd6c4b6" has successfully progressed.
      reason: NewReplicaSetAvailable
      status: "True"
      type: Progressing
    - lastTransitionTime: "2020-06-28T10:13:23Z"
      lastUpdateTime: "2020-06-28T10:13:23Z"
      message: Deployment has minimum availability.
      reason: MinimumReplicasAvailable
      status: "True"
      type: Available
    observedGeneration: 1
    readyReplicas: 1
    replicas: 1
    updatedReplicas: 1

The expected status of federated deployment is something like.

  status:
    clusters:
    - name: paco81
      availableReplicas: 1
      readyReplicas: 1
      replicas: 1
      updatedReplicas: 1
    - name: cluster0
      availableReplicas: 1
      observedGeneration: 1
      readyReplicas: 1
      replicas: 1
      updatedReplicas: 1
    conditions:
    - lastTransitionTime: "2020-06-30T02:23:45Z"
      lastUpdateTime: "2020-06-30T02:42:22Z"
      status: "True"
      type: Propagation
    observedGeneration: 2

Why is this needed:
In federated resource aspect, we can see READY instances number and available instances numbers like deployment.

[root@dce-10-7-177-8 .kube]# kubectl get deployment
NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
cloudevents-go-7nvpc-deployment   1/1     1            1           23h
dao-2048-dao-2048                 1/1     1            1           24h

For workloads like deployment/replicasets/statefulsets/daemonset, the status of each cluster would be shown in federated instances.

/kind feature

[RainbowMango]

@pacoxu Thanks, I'm glad to hear from you.
We are discussing how to add generic status for all kinds of federated resources at #1237. You are welcome to join in.

In my opinion, your request is totally reasonable, let's see how to accomplish it.

[pacoxu]

From federated deployment controller side, this status would help a lot in rebalance scenario like below.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[hectorj2f]

/remove-lifecycle stale

[hectorj2f]

/assign @hectorj2f

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[hectorj2f]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[pacoxu]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.