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

Apply changes to service resource #159

Merged

Conversation

ironcladlou
Copy link
Contributor

@ironcladlou ironcladlou commented Mar 19, 2020

Add support for applying changes to the service resource. Roll back 8ae4b02
since service topology feature gate isn't yet enabled, and add TODOs to
re-introduce support when the gate is finally enabled.

Part of, but not a complete fix for https://bugzilla.redhat.com/show_bug.cgi?id=1805177 because the service topology feature gate isn't enabled. Without that gate, service.spec.toplogyKey won't be persisted.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Mar 19, 2020
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1805177: WIP: Apply changes to service resource

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 Author

cc @Miciah

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 19, 2020
@ironcladlou ironcladlou changed the title Bug 1805177: WIP: Apply changes to service resource Bug 1805177: Apply changes to service resource Mar 19, 2020
@ironcladlou
Copy link
Contributor Author

I still need to do e2e testing of this.

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 20, 2020
@ironcladlou ironcladlou changed the title Bug 1805177: Apply changes to service resource Apply changes to service resource Mar 24, 2020
@openshift-ci-robot openshift-ci-robot removed the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Mar 24, 2020
@openshift-ci-robot
Copy link
Contributor

@ironcladlou: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Apply changes to service resource

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 Author

/hold cancel

@Miciah want to go ahead and merge this?

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 24, 2020
@ironcladlou
Copy link
Contributor Author

/hold

Wait for #159 and then rebase

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 24, 2020
@Miciah
Copy link
Contributor

Miciah commented Mar 25, 2020

@ironcladlou
Copy link
Contributor Author

It doesn't get persisted — you're right, if we want to keep the general diff/apply logic I should remove serviceTopology entirely from the PR for now.

@ironcladlou ironcladlou force-pushed the apply-topology-keys branch 2 times, most recently from c2dd802 to a9d8d33 Compare March 26, 2020 13:01
@ironcladlou
Copy link
Contributor Author

/hold cancel

@Miciah I rebased and updated the goal of this PR. PTAL.

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 26, 2020
Copy link
Contributor

@frobware frobware left a comment

Choose a reason for hiding this comment

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

Might be better to split the rollback into a discrete commit, if possible.

LGTM bar the additional explicit test case to add.

Leaving to @Miciah to tag as he had more comments first time round.

expect: true,
},
{
description: "if .spec.publishNotReadyAddresses changes",
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe add a test for field Spec.ClusterIP as we call that out explicitly in serviceChanged()?

// Preserve fields that the API, other controllers, or user may have
// modified.
updated.Spec.ClusterIP = current.Spec.ClusterIP

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

The feature gate to support this isn't enabled yet.
Add support for applying changes to the service resource. Since the service
topology feature gate isn't yet enabled, and add TODOs to re-introduce support
when the gate is finally enabled.
@ironcladlou
Copy link
Contributor Author

Might be better to split the rollback into a discrete commit, if possible.

Done

@frobware
Copy link
Contributor

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [frobware,ironcladlou]

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 b6fa3cb into openshift:master Mar 30, 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants