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 1801410: Set affinity for "NodePortService" #357

Conversation

Miciah
Copy link
Contributor

@Miciah Miciah commented Feb 10, 2020

Configure the same deployment strategy and affinity policy on the deployment for an IngressController that uses the "NodePortService" endpoint publishing strategy type as we do for an IngressController that uses the "LoadBalancerService" or "Private" strategy type.

Follow-up to #343.

  • pkg/operator/controller/ingress/deployment.go (desiredRouterDeployment): Configure deployment strategy and affinity policy the same for "NodePortService" as for "LoadBalancerService" and "Private".

Configure the same deployment strategy and affinity policy on the
deployment for an IngressController that uses the "NodePortService"
endpoint publishing strategy type as we do for an IngressController that
uses the "LoadBalancerService" or "Private" strategy type.

Follow-up to commit 3d9a5d3.

This commit fixes bug 1801410

https://bugzilla.redhat.com/show_bug.cgi?id=1801410

* pkg/operator/controller/ingress/deployment.go
(desiredRouterDeployment): Configure deployment strategy and affinity
policy the same for "NodePortService" as for "LoadBalancerService" and
"Private".
@openshift-ci-robot
Copy link
Contributor

@Miciah: This pull request references Bugzilla bug 1801410, 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.

In response to this:

Bug 1801410: Set affinity for "NodePortService"

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 bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 10, 2020
@Miciah
Copy link
Contributor Author

Miciah commented Feb 10, 2020

/cherry-pick release-4.4

@openshift-cherrypick-robot

@Miciah: once the present PR merges, I will cherry-pick it on top of release-4.4 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.4

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.

@ironcladlou
Copy link
Contributor

/lgtm
/retest

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ironcladlou, Miciah

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-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit f7bc7a9 into openshift:master Feb 11, 2020
@openshift-ci-robot
Copy link
Contributor

@Miciah: All pull requests linked via external trackers have merged. Bugzilla bug 1801410 has been moved to the MODIFIED state.

In response to this:

Bug 1801410: Set affinity for "NodePortService"

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-cherrypick-robot

@Miciah: new pull request created: #358

In response to this:

/cherry-pick release-4.4

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.

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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants