{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/76938","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/76938/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/76938/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/76938/events","html_url":"https://github.com/kubernetes/kubernetes/issues/76938","id":436168300,"node_id":"MDU6SXNzdWU0MzYxNjgzMDA=","number":76938,"title":"undesired number of replica sets are created during deployment update","user":{"login":"petro404","id":47523330,"node_id":"MDQ6VXNlcjQ3NTIzMzMw","avatar_url":"https://avatars2.githubusercontent.com/u/47523330?v=4","gravatar_id":"","url":"https://api.github.com/users/petro404","html_url":"https://github.com/petro404","followers_url":"https://api.github.com/users/petro404/followers","following_url":"https://api.github.com/users/petro404/following{/other_user}","gists_url":"https://api.github.com/users/petro404/gists{/gist_id}","starred_url":"https://api.github.com/users/petro404/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/petro404/subscriptions","organizations_url":"https://api.github.com/users/petro404/orgs","repos_url":"https://api.github.com/users/petro404/repos","events_url":"https://api.github.com/users/petro404/events{/privacy}","received_events_url":"https://api.github.com/users/petro404/received_events","type":"User","site_admin":false},"labels":[{"id":105146071,"node_id":"MDU6TGFiZWwxMDUxNDYwNzE=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/kind/bug","name":"kind/bug","color":"e11d21","default":false},{"id":778118402,"node_id":"MDU6TGFiZWw3NzgxMTg0MDI=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/lifecycle/rotten","name":"lifecycle/rotten","color":"604460","default":false},{"id":125010198,"node_id":"MDU6TGFiZWwxMjUwMTAxOTg=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/scalability","name":"sig/scalability","color":"d2b48c","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2019-04-23T12:46:32Z","updated_at":"2019-09-20T16:16:58Z","closed_at":"2019-09-20T16:16:57Z","author_association":"NONE","body":"<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!\r\n\r\nIf the matter is security related, please disclose it privately via https://kubernetes.io/security/\r\n-->\r\n\r\n\r\n**What happened**:\r\nI am running client in golang which is using k8s to create deployment resource and HorizontalPodAutoscaler\r\nI am not defining replicaset as part of the deployment resource so it used the default 1\r\nHorizontalPodAutoscaler us defined with mix=max=1\r\n\r\nThe current behavior:\r\n2 replica set are created then 2 pods are created then the HorizontalPodAutoscaler take care to reset one replica and kill the pod so the end state is ok\r\n\r\n\r\nIs this normal behavior as I am updating the deployment resource during my flow so rolling update flow is running therefore 2 replica sets are created?\r\n\r\n> \r\n>  Events Flow:\r\n> Deployment  Normal    ScalingReplicaSet              deployment-controller         Scaled up replica set example-ms-76896c7f7f to 1\r\n> Deployment  Normal    ScalingReplicaSet              deployment-controller         Scaled up replica set example-ms-6c9dbcbc74 to 1\r\n> HorizontalPodAutoscaler             Normal    SuccessfulRescale   horizontal-pod-autoscaler   New size: 1; reason: Current number of replicas above Spec.MaxReplicas\r\n> Deployment             Normal    ScalingReplicaSet   deployment-controller   Scaled down replica set example-ms-76896c7f7f to 0\r\n> ReplicaSet             Normal    SuccessfulDelete   replicaset-controller   Deleted pod: example-ms-76896c7f7f-kbfsz\r\n> \r\n\r\n\r\n\r\n**What you expected to happen**:\r\n1 replica set should be created\r\n\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\n\r\n**Anything else we need to know?**:\r\n\r\n**Environment**:\r\n- Kubernetes version (use `kubectl version`):\r\nv.11.0\r\n- Cloud provider or hardware configuration:\r\n- OS (e.g: `cat /etc/os-release`):\r\n- Kernel (e.g. `uname -a`):\r\n- Install tools:\r\n- Network plugin and version (if this is a network-related bug):\r\n- Others:\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/533619497","html_url":"https://github.com/kubernetes/kubernetes/issues/76938#issuecomment-533619497","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/76938","id":533619497,"node_id":"MDEyOklzc3VlQ29tbWVudDUzMzYxOTQ5Nw==","user":{"login":"k8s-ci-robot","id":20407524,"node_id":"MDQ6VXNlcjIwNDA3NTI0","avatar_url":"https://avatars0.githubusercontent.com/u/20407524?v=4","gravatar_id":"","url":"https://api.github.com/users/k8s-ci-robot","html_url":"https://github.com/k8s-ci-robot","followers_url":"https://api.github.com/users/k8s-ci-robot/followers","following_url":"https://api.github.com/users/k8s-ci-robot/following{/other_user}","gists_url":"https://api.github.com/users/k8s-ci-robot/gists{/gist_id}","starred_url":"https://api.github.com/users/k8s-ci-robot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/k8s-ci-robot/subscriptions","organizations_url":"https://api.github.com/users/k8s-ci-robot/orgs","repos_url":"https://api.github.com/users/k8s-ci-robot/repos","events_url":"https://api.github.com/users/k8s-ci-robot/events{/privacy}","received_events_url":"https://api.github.com/users/k8s-ci-robot/received_events","type":"User","site_admin":false},"created_at":"2019-09-20T16:16:58Z","updated_at":"2019-09-20T16:16:58Z","author_association":"CONTRIBUTOR","body":"@fejta-bot: Closing this issue.\n\n<details>\n\nIn response to [this](https://github.com/kubernetes/kubernetes/issues/76938#issuecomment-533619448):\n\n>Rotten issues close after 30d of inactivity.\n>Reopen the issue with `/reopen`.\n>Mark the issue as fresh with `/remove-lifecycle rotten`.\n>\n>Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).\n>/close\n\n\nInstructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.\n</details>"}}
{"actor":{"display_login":"k8s-ci-robot"}}