-
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
UPSTREAM: attach must only allow a tty when container supports it #5497
Conversation
For the record, |
@fabianofranz I don't think this is the right fix. if the container in the pod isn't configured with TTY=true (https://github.com/kubernetes/kubernetes/blob/master/pkg/api/v1/types.go#L993), then we shouldn't allow |
cf0fa32
to
f5a3318
Compare
PR refactored, @ncdc please take a look. |
@fabianofranz would you mind updating the title and description of this PR? Does attach work if container.Stdin is false? Should we check for that too? |
@ncdc updated. stdin works fine, tested with https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/pods/pod_with_two_containers.json. |
[test] |
Attach allows stdin=false. On Thu, Oct 29, 2015 at 2:33 PM, Andy Goldstein [email protected]
|
f5a3318
to
bb456b7
Compare
Upstream PR: kubernetes/kubernetes#16537 |
bb456b7
to
5fbb045
Compare
5fbb045
to
398ad3a
Compare
Evaluated for origin test up to 398ad3a |
@openshift/team-project-committers upstream PR is merging. |
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/6597/) |
LGTM [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/3913/) (Image: devenv-rhel7_2632) |
Evaluated for origin merge up to 398ad3a |
Fixes bug 1270685 https://bugzilla.redhat.com/show_bug.cgi?id=1270685
If a container does not support TTY, warn the user if
-t
was provided toattach
.