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 1839517: UPSTREAM: <carry>: kube-controller-manager: allow running bare kube-controller-manager #25037

Merged
merged 1 commit into from May 29, 2020

Conversation

soltysh
Copy link
Member

@soltysh soltysh commented May 27, 2020

No description provided.

@soltysh soltysh changed the title UPSTREAM: <carry>: kube-controller-manager: allow running bare kube-controller-manager Bug 1839517: UPSTREAM: <carry>: kube-controller-manager: allow running bare kube-controller-manager May 27, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. label May 27, 2020
@openshift-ci-robot
Copy link

@soltysh: This pull request references Bugzilla bug 1839517, 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 1839517: UPSTREAM: : kube-controller-manager: allow running bare kube-controller-manager

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 bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label May 27, 2020
@openshift-ci-robot openshift-ci-robot added vendor-update Touching vendor dir or related files approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 27, 2020
@deads2k
Copy link
Contributor

deads2k commented May 27, 2020

Can you go in the other direction. If we pass no openshift data in the openshift config, let's stop using it and only pass flags in the pod

@soltysh
Copy link
Member Author

soltysh commented May 28, 2020

/retest

return kerrors.NewAggregate(err)
}
return nil
}

// applyFlags stores the provided arguments onto a flag set, reporting any errors
// encountered during the process.
func applyFlags(args map[string][]string, flags flag.NamedFlagSets) []error {
func applyFlags(args map[string][]string, flags *pflag.FlagSet) []error {
Copy link
Contributor

Choose a reason for hiding this comment

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

why is all this still needed?

Copy link
Member Author

Choose a reason for hiding this comment

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

Since we wire and pass these flag values, we can't break them. I don't want to end up in the situation where this stops working, although truth to be told, this never worked in past few releases 😓 In 4.6 this will be entirely dropped in favor of regular flag passing.

@soltysh
Copy link
Member Author

soltysh commented May 28, 2020

/retest

2 similar comments
@soltysh
Copy link
Member Author

soltysh commented May 28, 2020

/retest

@soltysh
Copy link
Member Author

soltysh commented May 28, 2020

/retest

@mfojtik
Copy link
Member

mfojtik commented May 28, 2020

/lgtm

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

deads2k commented May 28, 2020

good enough for half a release I guess
/lgtm

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, mfojtik, soltysh

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 [deads2k,mfojtik,soltysh]

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

@soltysh
Copy link
Member Author

soltysh commented May 28, 2020

/retest

@openshift-bot
Copy link
Contributor

/retest

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

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

/retest

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

@soltysh
Copy link
Member Author

soltysh commented May 29, 2020

/retest

@openshift-merge-robot openshift-merge-robot merged commit 917867d into openshift:master May 29, 2020
@openshift-ci-robot
Copy link

@soltysh: All pull requests linked via external trackers have merged: openshift/origin#25037. Bugzilla bug 1839517 has been moved to the MODIFIED state.

In response to this:

Bug 1839517: UPSTREAM: : kube-controller-manager: allow running bare kube-controller-manager

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.

@soltysh soltysh deleted the bug1839517 branch May 29, 2020 17:30
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/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. 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. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants