-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Stop putting env vars into BoundPods. #4359
Conversation
LGTM So nice. |
Do the Red Hat folks have concerns? |
None. |
not sure why integration test failed on go1.4 on travis. Works for me and shippable and travis+1.3 |
@erictune Could you rebase please |
They will still show up in etcd. They never were available through the API. A subsequent PR(s) will rip out all BoundPods code. Working in small increments. This PR will cause users on lagging cloud providers to not get env vars in their pods if they update to this code. They have already been warned via email. Removed unit tests of BasicBoundPodFactory. There is adequate coverage in pkg/kubelet/kubelet_test.go.
1953014
to
5b45696
Compare
@saad-ali rebased |
Stop putting env vars into BoundPods.
Does this close #4176? |
no On Thu, Feb 12, 2015 at 11:19 AM, Zach Loafman notifications@github.com
|
and by "no" I mean yes. On Thu, Feb 12, 2015 at 11:21 AM, Eric Tune etune@google.com wrote:
|
They will still show up in etcd. They never were available
through the API.
A subsequent PR(s) will rip out all BoundPods code.
Working in small increments.
This PR will cause users on lagging cloud providers
to not get env vars in their pods if they update to this code.
They have already been warned via email.
Removed unit tests of BasicBoundPodFactory.
There is adequate coverage in pkg/kubelet/kubelet_test.go.