Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kubelet should know which containers it is managing #4

Closed
jbeda opened this issue Jun 6, 2014 · 1 comment
Closed

kubelet should know which containers it is managing #4

jbeda opened this issue Jun 6, 2014 · 1 comment

Comments

@jbeda
Copy link
Contributor

jbeda commented Jun 6, 2014

Right now the kubelet will assume that it is in charge of all containers on a machine. That means you can't mix/match kubelet managed containers and non-kubelet managed containers.

Instead, we should have kubelet mark those containers it is managing (perhaps either storing them locally or putting more stuff into the container name or, eventually, using docker supported container labels) and only kill/curate those.

@lavalamp says:

A simple hack to accomplish this is only pay attention to containers for which strings.Split(container_name, "--")[2] parses as an int (w/ appropriate error checking, of course). The names we generate are sufficiently obscure that this should be good enough for the moment.
brendandburns added a commit that referenced this issue Jun 9, 2014
@brendandburns
Merge pull request #30 from brendandburns/pod
8e8bc40 
Task -> Pod #4, the final chapter
lavalamp added a commit that referenced this issue Jun 13, 2014
@lavalamp
Merge pull request #98 from brendandburns/container_info
6d4e163 
Only manage containers with '--' in the name.  Addresses #4
@brendandburns
Copy link
Contributor

Handled by #98 for now. We might re-open later.

@jbeda jbeda mentioned this issue Jun 14, 2014
Closed
pmorie referenced this issue in pmorie/kubernetes Jul 23, 2014
@ironcladlou
Merge pull request #4 from ncdc/build-poc-andy
1525119 
Add jobs support to Client
@markllama markllama mentioned this issue Sep 10, 2014
Merged
@darkgaro darkgaro mentioned this issue Oct 16, 2014
Closed
@smarterclayton smarterclayton mentioned this issue Nov 3, 2014
Closed
vmarmol referenced this issue in vmarmol/kubernetes Nov 17, 2014
@vmarmol
Merge pull request #4 from vmarmol/master
a9abd60 
Add ability to add instances via cloudprovider
jwhonce pushed a commit to jwhonce/kubernetes that referenced this issue Dec 11, 2014
@markturansky
Merge pull request kubernetes#4 from markturansky/pd_dev
4231fd1 
Pd dev
EricMountain-1A pushed a commit to EricMountain-1A/kubernetes that referenced this issue Feb 6, 2015
@pmorie
Merge pull request kubernetes#4 from EricMountain-1A/secrets_proposal…
fa7b6bb 
…_pmorie

Beginnings of registry for secrets (no REST API yet).
@j3ffml j3ffml mentioned this issue Mar 30, 2015
Closed
@kcao3 kcao3 mentioned this issue May 19, 2015
Closed
@andrewhampton andrewhampton mentioned this issue Jul 28, 2015
Merged
@asridharan asridharan mentioned this issue Aug 10, 2015
Closed
@lvlv lvlv mentioned this issue Aug 17, 2015
Closed
@rajnemani rajnemani mentioned this issue Aug 24, 2015
Merged
mkulke pushed a commit to mkulke/kubernetes that referenced this issue Sep 22, 2015
Use "nonResourcePath" property in policy to expose custom endpoints.
29d267a 
Fixed indents and replaced 'kind' w/ 'resource'.

Fixed some more indents.

Tests: Replaced kind w/ resource once again, some minor tweaks.

Fixed indents.

Fixed indents.

Only use the API request resolver on actual api prefixed requests.

Updated doc for swagger policies.

Address gofmt complaints.

Consider api prefixes with more than 1 path fragment. ("api/123")

Fix: incrementor missing.

Refactored and tests added.

Allow trailing slash.

Addressed kubernetes#3, kubernetes#4, kubernetes#6, kubernetes#5, kubernetes#8, kubernetes#7

Enforce non-resource auth on all users, not only ns'ed.

Conflicts:
	docs/admin/authorization.md
	pkg/apiserver/handlers_test.go
	pkg/auth/authorizer/abac/abac_test.go
mkulke pushed a commit to mkulke/kubernetes that referenced this issue Sep 22, 2015
Use "nonResourcePath" property in policy to expose custom endpoints.
02b81f5 
Fixed indents and replaced 'kind' w/ 'resource'.

Fixed some more indents.

Tests: Replaced kind w/ resource once again, some minor tweaks.

Fixed indents.

Fixed indents.

Only use the API request resolver on actual api prefixed requests.

Updated doc for swagger policies.

Address gofmt complaints.

Consider api prefixes with more than 1 path fragment. ("api/123")

Fix: incrementor missing.

Refactored and tests added.

Allow trailing slash.

Addressed kubernetes#3, kubernetes#4, kubernetes#6, kubernetes#5, kubernetes#8, kubernetes#7

Enforce non-resource auth on all users, not only ns'ed.

Conflicts:
	docs/admin/authorization.md
	pkg/apiserver/handlers_test.go
	pkg/auth/authorizer/abac/abac_test.go
feiskyer referenced this issue in feiskyer/kubernetes Oct 14, 2015
@feiskyer
Merge pull request #4 from carmark/auth
1380c03 
Tenant and Auth
@jcderr jcderr mentioned this issue Nov 6, 2015
Closed
@screeley44 screeley44 mentioned this issue Mar 31, 2016
Closed
dagnello pushed a commit to dagnello/kubernetes that referenced this issue Apr 7, 2016
@vipulsabhaya
Merge pull request kubernetes#4 from abithap/vsphere
38e8bd0 
Initial commit of vSphere cloud provider
@mfanjie mfanjie mentioned this issue May 18, 2016
Closed
@samsonahk samsonahk mentioned this issue Jun 28, 2019
Closed
@BobyMCbobs BobyMCbobs mentioned this issue Dec 16, 2019
Closed
3 tasks
@atheurer atheurer mentioned this issue Jan 28, 2020
Closed
cynepco3hahue referenced this issue in cynepco3hahue/kubernetes Mar 15, 2020
Merge pull request #4 from cynepco3hahue/comments_fixes
74d7de0 
Generate bazel files and fix previous comments
whypro pushed a commit to whypro/kubernetes that referenced this issue Sep 17, 2020
@Sreemanti-Ghosh
Socket mask unit test (kubernetes#4)
8c6c4e6
@saschagrunert saschagrunert mentioned this issue Jan 29, 2021
Merged
@kevindelgado kevindelgado mentioned this issue Feb 12, 2021
Closed
@dims dims mentioned this issue Feb 19, 2021
Merged
pohly referenced this issue in pohly/kubernetes Mar 1, 2021
@pohly
e2e test: use one connection per stream
06ffdbc 
Sharing the same connection for multiple streams should have worked,
but ran into unexpected timeouts:

I0227 08:07:49.754263   80029 portproxy.go:109] container "mock" in pod csi-mock-volumes-4037-2061/csi-mockplugin-0 is running
E0227 08:07:49.779359   80029 portproxy.go:178] prepare forwarding csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: dialer failed: unable to upgrade connection: pod not found ("csi-mockplugin-0_csi-mock-volumes-4037-2061")
I0227 08:07:50.782705   80029 portproxy.go:109] container "mock" in pod csi-mock-volumes-4037-2061/csi-mockplugin-0 is running
I0227 08:07:50.809326   80029 portproxy.go:125] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: starting connection polling
I0227 08:07:50.909544   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #0, 0 open
I0227 08:07:50.912436   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #0
I0227 08:07:50.912503   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #0
I0227 08:07:50.913161   80029 portproxy.go:322] forward connection #0 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: remote side closed the stream
E0227 08:07:50.913324   80029 portproxy.go:242] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: an error occurred connecting to the remote port: error forwarding port 9000 to pod 66662ea1ab30b4193dac0102c49be840971d337c802cc0c8bbc074214522bd13, uid : failed to execute portforward in network namespace "/var/run/netns/cni-c15e4e36-dad9-8316-c301-33af9dad5717": failed to dial 9000: dial tcp4 127.0.0.1:9000: connect: connection refused
I0227 08:07:50.913371   80029 portproxy.go:340] forward connection #0 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: closing our side
W0227 08:07:50.913487   80029 server.go:669] grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams failed to receive the preface from client: EOF"
I0227 08:07:51.009519   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #1, 0 open
I0227 08:07:51.011912   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #1
I0227 08:07:51.011973   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #1
I0227 08:07:51.013677   80029 portproxy.go:322] forward connection #1 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: remote side closed the stream
I0227 08:07:51.013720   80029 portproxy.go:340] forward connection #1 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: closing our side
W0227 08:07:51.013794   80029 server.go:669] grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams failed to receive the preface from client: EOF"
E0227 08:07:51.017026   80029 portproxy.go:242] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: an error occurred connecting to the remote port: error forwarding port 9000 to pod 66662ea1ab30b4193dac0102c49be840971d337c802cc0c8bbc074214522bd13, uid : failed to execute portforward in network namespace "/var/run/netns/cni-c15e4e36-dad9-8316-c301-33af9dad5717": failed to dial 9000: dial tcp4 127.0.0.1:9000: connect: connection refused
I0227 08:07:51.109515   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #2, 0 open
I0227 08:07:51.111479   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #2
I0227 08:07:51.111519   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #2
I0227 08:07:51.209519   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #3, 1 open
I0227 08:07:51.766305   80029 csi.go:377] gRPC call: {"Method":"/csi.v1.Identity/Probe","Request":{},"Response":{"ready":{"value":true}},"Error":"","FullError":null}
I0227 08:07:51.768304   80029 csi.go:377] gRPC call: {"Method":"/csi.v1.Identity/GetPluginInfo","Request":{},"Response":{"name":"csi-mock-csi-mock-volumes-4037","vendor_version":"0.3.0","manifest":{"url":"https://k8s.io/kubernetes/test/e2e/storage/drivers/csi-test/mock"}},"Error":"","FullError":null}
I0227 08:07:51.770494   80029 csi.go:377] gRPC call: {"Method":"/csi.v1.Identity/GetPluginCapabilities","Request":{},"Response":{"capabilities":[{"Type":{"Service":{"type":1}}},{"Type":{"VolumeExpansion":{"type":1}}},{"Type":{"Service":{"type":2}}}]},"Error":"","FullError":null}
I0227 08:07:51.772899   80029 csi.go:377] gRPC call: {"Method":"/csi.v1.Controller/ControllerGetCapabilities","Request":{},"Response":{"capabilities":[{"Type":{"Rpc":{"type":1}}},{"Type":{"Rpc":{"type":3}}},{"Type":{"Rpc":{"type":10}}},{"Type":{"Rpc":{"type":4}}},{"Type":{"Rpc":{"type":6}}},{"Type":{"Rpc":{"type":5}}},{"Type":{"Rpc":{"type":8}}},{"Type":{"Rpc":{"type":7}}},{"Type":{"Rpc":{"type":12}}},{"Type":{"Rpc":{"type":11}}},{"Type":{"Rpc":{"type":9}}}]},"Error":"","FullError":null}
I0227 08:08:21.209901   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating error stream: Timeout occurred
I0227 08:08:21.209980   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #3, 1 open
I0227 08:08:51.211522   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating data stream: Timeout occurred
I0227 08:08:51.211566   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #3, 1 open
I0227 08:08:51.213451   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #3
I0227 08:08:51.213498   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #3
I0227 08:08:51.309540   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #4, 2 open
I0227 08:08:52.215358   80029 portproxy.go:322] forward connection #3 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: remote side closed the stream
I0227 08:08:52.215475   80029 portproxy.go:340] forward connection #3 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: closing our side
I0227 08:09:21.310003   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating error stream: Timeout occurred
I0227 08:09:21.310086   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #4, 1 open
I0227 08:09:51.311854   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating data stream: Timeout occurred
I0227 08:09:51.311908   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #4, 1 open
I0227 08:09:51.314415   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #4
I0227 08:09:51.314497   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #4
I0227 08:09:51.409527   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #5, 2 open
I0227 08:09:52.326203   80029 portproxy.go:322] forward connection #4 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: remote side closed the stream
I0227 08:09:52.326277   80029 portproxy.go:340] forward connection #4 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: closing our side
I0227 08:10:21.409892   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating error stream: Timeout occurred
I0227 08:10:21.409954   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #5, 1 open
I0227 08:10:51.411455   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating data stream: Timeout occurred
I0227 08:10:51.411557   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #5, 1 open
I0227 08:10:51.413229   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #5
I0227 08:10:51.413274   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #5
I0227 08:10:51.509508   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #6, 2 open
I0227 08:10:52.414862   80029 portproxy.go:322] forward connection #5 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: remote side closed the stream
I0227 08:10:52.414931   80029 portproxy.go:340] forward connection #5 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: closing our side
I0227 08:11:21.509879   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating error stream: Timeout occurred
I0227 08:11:21.509934   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #6, 1 open
I0227 08:11:51.511519   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating data stream: Timeout occurred
I0227 08:11:51.511568   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #6, 1 open
I0227 08:11:51.513519   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #6
I0227 08:11:51.513571   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #6
I0227 08:11:51.609504   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #7, 2 open
I0227 08:11:52.517799   80029 portproxy.go:322] forward connection #6 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: remote side closed the stream
I0227 08:11:52.517918   80029 portproxy.go:340] forward connection #6 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: closing our side
I0227 08:12:21.609856   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating error stream: Timeout occurred
I0227 08:12:21.609909   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #7, 1 open
I0227 08:12:51.611494   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating data stream: Timeout occurred
I0227 08:12:51.611555   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #7, 1 open
I0227 08:12:51.613289   80029 portproxy.go:155] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: created a new connection #7
I0227 08:12:51.613343   80029 portproxy.go:286] forward listener for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: got a new connection #7
I0227 08:12:51.709535   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #8, 2 open
I0227 08:12:52.615858   80029 portproxy.go:322] forward connection #7 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: remote side closed the stream
I0227 08:12:52.615989   80029 portproxy.go:340] forward connection #7 for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: closing our side
W0227 08:12:52.616116   80029 server.go:669] grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams failed to receive the preface from client: EOF"
I0227 08:13:21.709934   80029 portproxy.go:151] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: no connection: error creating error stream: Timeout occurred
I0227 08:13:21.709997   80029 portproxy.go:148] port forwarding for csi-mock-volumes-4037-2061/csi-mockplugin-0:9000: trying to create a new connection #8, 1 open
Feb 27 08:13:30.916: FAIL: Failed to register CSIDriver csi-mock-csi-mock-volumes-4037
Unexpected error:
    <*errors.errorString | 0xc002666220>: {
        s: "error waiting for CSI driver csi-mock-csi-mock-volumes-4037 registration on node kind-worker2: timed out waiting for the condition",
    }
    error waiting for CSI driver csi-mock-csi-mock-volumes-4037 registration on node kind-worker2: timed out waiting for the condition
occurred
@jackfrancis jackfrancis mentioned this issue May 7, 2021
Merged
@pagarwal-tibco pagarwal-tibco mentioned this issue Oct 22, 2021
Closed
@jsafrane jsafrane mentioned this issue Nov 16, 2021
Merged
@thockin thockin mentioned this issue Jul 12, 2022
Merged
ezrasilvera referenced this issue in ezrasilvera/kubernetes Nov 10, 2022
@stevekuznetsov
Merge pull request #4 from ezrasilvera/sk-generic-storage
d0f9541 
kubeadm: support crdb
@iholder101 iholder101 mentioned this issue Mar 15, 2023
Closed
@iholder101 iholder101 mentioned this issue Apr 16, 2023
Closed
@iholder101 iholder101 mentioned this issue Jun 28, 2023
Merged
@kishoremakkena kishoremakkena mentioned this issue Nov 26, 2023
Closed
wm775825 pushed a commit to wm775825/kubernetes that referenced this issue Dec 2, 2023
@XiShanYongYe-Chang
Merge pull request kubernetes#4 from wm775825/release-1.28
aa3bf99 
Add List handler
wm775825 pushed a commit to wm775825/kubernetes that referenced this issue Dec 18, 2023
@karmada-bot
Merge pull request kubernetes#4 from XiShanYongYe-Chang/v1.28.4-karmada
853a72a 
support exec with no proxy
@tallclair tallclair mentioned this issue May 3, 2024
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jbeda @brendandburns