Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[WIP] Add container command execution proposal #576

Closed
wants to merge 3 commits into from

Conversation

ncdc
Copy link
Contributor

@ncdc ncdc commented Dec 16, 2014

No description provided.

@ncdc
Copy link
Contributor Author

ncdc commented Dec 16, 2014

@smarterclayton @danmcp @jwhonce PTAL


A user must be able to specify the container or containers in which the requested command should run and/or the port forwarding should occur. A container is uniquely identified by the combination of a namespace, a pod name, and a container name.

Here are possible ways to specify one more more containers:
Copy link
Contributor

Choose a reason for hiding this comment

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

Should "one more more" be "one or more"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes to "one or more".

We won't support port forwarding to multiple containers. But we should consider supporting executing a command in multiple containers.

@ncdc ncdc force-pushed the remote-command-execution branch from cdfc8cd to 13bdf8e Compare December 16, 2014 17:14

There are multiple ways to copy data between the client and the container. Below are 3 possibilities.

#### Port Forwarding Command: `nsenter` + external helper
Copy link
Contributor

Choose a reason for hiding this comment

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

You called this out as not being considered up above, but then have something here. Clarify. (leaving this section in is probably better than taking it out)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Where did I say it isn't being considered?

Copy link
Contributor

Choose a reason for hiding this comment

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

Nm, I misread: "more than one".

Remove OpenShift specifics.
Clarify questions.
Update which capabilities are required.
@smarterclayton
Copy link
Contributor

Moved upstream

@ncdc ncdc deleted the remote-command-execution branch February 21, 2015 01:18
jpeeler pushed a commit to jpeeler/origin that referenced this pull request Feb 1, 2018
* correct bug in keyer

* fix wrong kind in broker list

* add mocked out k8s core apisever client for tpr testing
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants