-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
use the upstream construction for kubeconfig evaluation #19335
use the upstream construction for kubeconfig evaluation #19335
Conversation
0035066
to
04b10a4
Compare
Interesting that test cmd succeeds and the clusterup install fails |
@pmorie I finally got it in CI!
|
/test extended_clusterup To see if the error is reproducible as I've done it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left you some comments. My biggest worries are around 62469, since it's clearly showing it's failing tons of stuff upstream. I'd like to see a green run in upstream and approval there before allowing this PR merge.
@@ -0,0 +1,222 @@ | |||
package router |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one sucks, a bit. Is there a plan to clean it up later on?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one sucks, a bit. Is there a plan to clean it up later on?
I was planning on never touching it again.
@knobunc @pravisankar this is highlighting that the router uses a different construction for kubeconfig flags and files than anyone else. It was already like this. This pull just makes it very obvious.
@@ -179,7 +179,11 @@ func DefaultClientConfig(flags *pflag.FlagSet) clientcmd.ClientConfig { | |||
// DEPRECATED: remove and replace with something more accurate | |||
loadingRules.DefaultClientConfig = &clientcmd.DefaultClientConfig | |||
|
|||
flags.StringVar(&loadingRules.ExplicitPath, "kubeconfig", "", "Path to the kubeconfig file to use for CLI requests.") | |||
if clientcmd.UseOpenShiftKubeConfigValues { | |||
flags.StringVar(&loadingRules.ExplicitPath, clientcmd.OpenShiftKubeConfigFlagName, "", "Path to the kubeconfig file to use for CLI requests.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While you're at it, since as the followup I'll revive the kubeconfig PR I have, maybe we can just squash both changes so that kubeconfig
is present always, we'll need it either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While you're at it, since as the followup I'll revive the kubeconfig PR I have, maybe we can just squash both changes so that kubeconfig is present always, we'll need it either way.
I'd rather not extend this pull further if we can avoid it.
Our needs are different. We have always done this, so it's actually parity for us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed the 62469 stuff with David on IRC. We have it already covered in https://github.com/openshift/origin/pull/19335/files#diff-5a19ec5edece86a33eb6c3c7a9ddd56aR205
In that case:
/lgtm
/retest Please review the full test history for this PR and help us cut down flakes. |
04b10a4
to
6f28a10
Compare
New changes are detected. LGTM label has been removed. |
6f28a10
to
156c979
Compare
New changes are detected. LGTM label has been removed. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, 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:
Approvers can indicate their approval by writing |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
use the upstream construction for kubeconfig evaluation
This changes our kubeconfig construction to use the upstream method with three patches
oc login
@openshift/sig-master
/assign @soltysh
@mfojtik @liggitt in combination with #19327, you'll be able to use the stock factory construction.