Skip to content

ReplicationController cannot fully reconcile with DeploymentReplicaSetTerminatingReplicas FG enabled #131821

Closed
@atiratree

Description

@atiratree

What happened?

extra syncs in KCM log

replica_set_utils.go:67] "Updating status for : default/test, replicas 3->3 (need 3), fullyLabeledReplicas 3->3, readyReplicas 3->3, availableReplicas 3->3, terminatingReplicas nil->0, sequence No: 1->1" logger="replicationcontroller-controller"

This issue has been noticed and also desribed in #128546 (comment) by @liggitt

What did you expect to happen?

no extra syncs

How can we reproduce it (as minimally and precisely as possible)?

create a ReplicationController with DeploymentReplicaSetTerminatingReplicas FG enabled

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
Client Version: v1.32.3
Kustomize Version: v5.5.0
Server Version: v1.34.0-alpha.0.635+a5e3df5e6855d9

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.sig/appsCategorizes an issue or PR as relevant to SIG Apps.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    Status

    Closed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions