Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1769927: Persistent Deployment #451

Merged
merged 2 commits into from Jan 31, 2020
Merged

Bug 1769927: Persistent Deployment #451

merged 2 commits into from Jan 31, 2020

Conversation

ricardomaraschini
Copy link
Contributor

@ricardomaraschini ricardomaraschini commented Jan 27, 2020

This patch makes use of library-go ApplyDeployment() function to stomp over user provided changes. This way we ensure that image registry Deployment is always on the state we need it to be.

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jan 27, 2020
@openshift-ci-robot
Copy link
Contributor

@ricardomaraschini: This pull request references Bugzilla bug 1769927, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

WIP - Bug 1769927: Persistent Deployment

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-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jan 27, 2020
@ricardomaraschini
Copy link
Contributor Author

/retest

pkg/resource/deployment.go Show resolved Hide resolved
pkg/resource/deployment.go Outdated Show resolved Hide resolved
@openshift-ci-robot
Copy link
Contributor

@ricardomaraschini: This pull request references Bugzilla bug 1769927, which is valid.

In response to this:

WIP - Bug 1769927: Persistent Deployment

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.

@ricardomaraschini
Copy link
Contributor Author

/retest

1 similar comment
@ricardomaraschini
Copy link
Contributor Author

/retest

@ricardomaraschini
Copy link
Contributor Author

/assign @dmage @adambkaplan

@ricardomaraschini ricardomaraschini changed the title WIP - Bug 1769927: Persistent Deployment Bug 1769927: Persistent Deployment Jan 28, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 28, 2020
@dmage
Copy link
Member

dmage commented Jan 29, 2020

@ricardomaraschini why do we need to bump dependencies in this PR?

@dmage
Copy link
Member

dmage commented Jan 29, 2020

@ricardomaraschini can you write an e2e test that patches the registry deployment and checks that this change is stomped?

@dmage
Copy link
Member

dmage commented Jan 29, 2020

/approve
otherwise it looks good

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 29, 2020
@ricardomaraschini
Copy link
Contributor Author

@ricardomaraschini why do we need to bump dependencies in this PR?

It happened when i added the new dependency on resourceapply package. I noticed it updated other stuff but I thought that it would not be bad to have them updated if possible.

@ricardomaraschini
Copy link
Contributor Author

@ricardomaraschini can you write an e2e test that patches the registry deployment and checks that this change is stomped?

Yes.

@ricardomaraschini
Copy link
Contributor Author

@dmage test implemented, PTAL.

}

// give some room for the operator to restore the deployment.
time.Sleep(10 * time.Second)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better to watch the resource. Or at least to poll. You never know how slow the CI machine can be.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a Poll here, PTAL.

This patch makes use of library-go ApplyDeployment() function to stomp
over user provided changes. This way we ensure that image registry
Deployment is always on the state we need it to be.
@ricardomaraschini
Copy link
Contributor Author

/retest

@dmage
Copy link
Member

dmage commented Jan 31, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 31, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dmage, ricardomaraschini

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:

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

@openshift-merge-robot openshift-merge-robot merged commit a140fc1 into openshift:master Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants