Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Powered by
Title
b
bored-farmer-36655
04/16/2023, 9:39 PM
@miniature-agent-31894
Hi you mean shell access? If so see <
https://kubernetes.io/docs/tasks/debug/debug-application/get-shell-running-container/
>
m
miniature-agent-31894
04/17/2023, 4:07 AM
The reason I asked this question is, I am not able to see any kube-proxy pod in the kube-system namespace because in the docs it is mentioned that, all the services like kube-proxy, kube-schedular run as part of the binary only
So, is there a way to access it from the bimary
3 Views
#k3s
Join Slack