-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Remove deprecatedPublicIPs field #44519
Remove deprecatedPublicIPs field #44519
Conversation
@thockin Did you generate |
@@ -1,2469 +0,0 @@ | |||
/* |
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.
Please check this generated file:)
@@ -141,7 +141,7 @@ cat << EOF > fe-s.json | |||
"ports": [{ | |||
"port": 3000 | |||
}], | |||
"deprecatedPublicIPs":["$PUBLIC_IP","10.1.4.89"], | |||
"externalIPs":["$PUBLIC_IP","10.1.4.89"], |
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.
Also change the name of $PUBLIC_IP
to EXTERNAL_IP
appears in this script?
bcc58c2
to
54447d1
Compare
54447d1
to
adfb2ca
Compare
adfb2ca
to
9153bfa
Compare
@caesarxuchao I don't know what to do wrt staging updates. I ran update-staging-client (update-all) and it made a bunch of changes like the following, which seem wrong.
|
The Jenkins verification passed anyway because we ignore the BUILD file diffs: https://github.com/kubernetes/kubernetes/blob/master/staging/copy.sh#L220-L221. @thockin if you run hack/update-bazel.sh again, are those changes cancelled? I don't know which script is managing the BUILD files in the staging folder, @mikedanese do you know? |
I manually reverted the obviously broken BUILD changes.
This is not a good developer experience. I made a simple API change, I had
to run godep restore, manually revert BUILD files, and mess with my
GOPATH. A casual contributor would have given up. *I* almost gave up.
…On Mon, Apr 17, 2017 at 10:25 AM, Chao Xu ***@***.***> wrote:
The Jenkins verification passed anyway because we ignore the BUILD file
diffs: https://github.com/kubernetes/kubernetes/blob/master/
staging/copy.sh#L220-L221. @thockin <https://github.com/thockin> if you
run hack/update-bazel.sh again, are those changes cancelled?
I don't know which script is managing the BUILD files in the staging
folder, @mikedanese <https://github.com/mikedanese> do you know?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44519 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVHZvY0vtXa4dLYA1KXKJ3LLgnFKAks5rw6B7gaJpZM4M-JcP>
.
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowei, thockin
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Gahh, that's a bug in how ./staging/copy.sh handles BUILD files, ./hack/update-bazel.sh is canonical. I'll take a look. |
@mikedanese it seems the problem is exposed by #40777 |
Chao: the staging scripts assume they can call godep-restore, but without a
clean GOPATH that can fail in a hundred different ways, leaving the user
confused and frustrated. It really needs to make a temporary space, change
GOPATH, restore into that, then process. It sucks. We should not be
asking users to do this.
…On Mon, Apr 17, 2017 at 10:38 AM, Mike Danese ***@***.***> wrote:
Gahh, that's a bug in how ./staging/copy.sh handles BUILD files,
./hack/update-bazel.sh is canonical. I'll take a look.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44519 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVJCx5dOkL-xeELaDOgj4u6rH-V0Uks5rw6OXgaJpZM4M-JcP>
.
|
Automatic merge from submit-queue |
On Mon, Apr 17, 2017 at 12:44 PM, Chao Xu ***@***.***> wrote:
@thockin the update-staging-client-go.sh verifies the working dir is clean before proceeding. Or do you mean other things by "clean GOPATH"?
If you have github.com/foobar in your own GOPATH, and then you do a
`godep restore` which includes that same package at a different rev it
can fail in a dozen different ways.
What I had to do to make it pass was:
mkdir _gopath
GOPATH=`pwd`/_gopath ./hack/godep-restore.sh
GOPATH=`pwd`/_gopath:$GOPATH ./hack/update-staging-client.sh
It really needs to make a temporary space, change GOPATH, restore into that, then process
We had considered this, but it will take too long to run.
The alternative is that it fails in hard to comprehend ways. We
should not be making users do this at all.
|
In general, i think we should focus on eliminating the staging folder, instead of building more tools around it. |
No description provided.