Bug 2099499: Backport resourceapply changes for being able to recreate daemonsets/deployments

[lobziik]

Manually cherry-picked resourceapply related changes from
#174

Several commits from this patchset was cherry-picked and then squashed together.

Such changes introduces recreation logic for daemonsets/deployments in case if
selectors was changed. Also, this contains respective tests changes.

Commits which was using for prepare this patch:

e1f47b7
1bf44f1
d4b6c3f
5b17fa2
a496360
9429f58
7488432

[openshift-ci]

@lobziik: This pull request references Bugzilla bug 2099499, which is invalid:

• expected the bug to target the "4.10.z" release, but it targets "---" instead
• expected Bugzilla bug 2099499 to depend on a bug targeting a release in 4.11.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2099499: Backport resourceapply changes for being able to recreate daemonsets/deployments

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.

[JoelSpeed]

/lgtm
/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 [JoelSpeed]

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

[JoelSpeed]

/bugzilla refresh

[openshift-ci]

@JoelSpeed: This pull request references Bugzilla bug 2099499, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.10.z) matches configured target release for branch (4.10.z)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 2051457 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2051457 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
• bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

/bugzilla refresh

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.

[openshift-ci]

@lobziik: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure-upgrade	0fffc47	link	false	/test e2e-azure-upgrade
ci/prow/e2e-azure-ccm	0fffc47	link	false	/test e2e-azure-ccm
ci/prow/e2e-vsphere-ccm-install	0fffc47	link	false	/test e2e-vsphere-ccm-install
ci/prow/e2e-openstack-ccm	0fffc47	link	false	/test e2e-openstack-ccm

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[sunzhaohua2]

/label cherry-pick-approved

[openshift-ci]

@lobziik: All pull requests linked via external trackers have merged:

• openshift/cluster-cloud-controller-manager-operator#194

Bugzilla bug 2099499 has been moved to the MODIFIED state.

In response to this:

Bug 2099499: Backport resourceapply changes for being able to recreate daemonsets/deployments

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.