You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 5 different pod definitions (YAML file), some contains from different pods need to have pid access from each other and I don't want to expose them at the host level by using hostPID: true.
I also can't move all container definitions to a single pod since those files are also used to test the application stack in a kubernetes cluster.
Is there a way to "force" a pod that was created by a kube-play command generated by quadlet in the same namespace? If not, are there other options?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have 5 different pod definitions (YAML file), some contains from different pods need to have pid access from each other and I don't want to expose them at the host level by using
hostPID: true
.I also can't move all container definitions to a single pod since those files are also used to test the application stack in a kubernetes cluster.
Is there a way to "force" a pod that was created by a kube-play command generated by quadlet in the same namespace? If not, are there other options?
Beta Was this translation helpful? Give feedback.
All reactions