kubernetes-sig-cli-feature-requests

exxocism left a comment (kubernetes/kubernetes#20227) Please — Reply to this email directly, view it

udayraj-rzp left a comment (kubernetes/kubernetes#52326) +1 — Reply to this email directly, view it

guettli left a comment (kubernetes/kubernetes#27308) I use direnv. For every environment I usually

As a workaround, I piped the output to sed and removed this useless message. | sed -r "s/tar:

As a workaround, for scripting, this could be used: if LANG=C kubectl apply -f change.yaml | grep -v

Closed #53459 as completed. — Reply to this email directly, view it on GitHub, or unsubscribe. You

kubectl with 1000 of awks and args nice that this is so easy. Is there really no affort to implmement

For anyone who is having trouble with this. You can try kubectl patch secret foo --type=json --patch-

this is a very late response to this thread, but kubectl-whoami supports windows as of Mar 2023. On

Any other way I could test that my PDB works if I can't delete pods and see that it doesn't

This might be helpful for others like me, who end up here via some search engine. :) Sorry for the

hi Tedezed thanks for the info. — Reply to this email directly, view it on GitHub, or unsubscribe.

sorry but changing one ugly solution by another? What was the problem to update the CHANGE-CAUSE

Not sure this is the good place to xreference as the issue is already closed, but potential users of

There is also a solution to set up port forwarding to a service without selector/pod (eg ExternalName

is there any update on this? still would be useful — Reply to this email directly, view it on GitHub,

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and

Closed #277 as completed. — Reply to this email directly, view it on GitHub, or unsubscribe. You are

AWS Cloud Lead Developer needed in Plano, TX, Columbus, OH, Wilmington, DE, or NY. Onsite position

Hello, Aarya here from Blink Technology Partners! At the moment, I am fulfilling the requirements of

This is a kubectl issue /transfer kubectl — Reply to this email directly, view it on GitHub, or

@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:

$ kubectl describe pvc -A | grep -E "Name|StorageClass|Used" Name: ocs-deviceset-lso-

Does this let you rename the cluster name? Yes, it does, try it out :) — Reply to this email directly

Test! $ helm create k8s-helm $ helm lint k8s-helm/ ==> Linting k8s-helm/ [INFO] Chart.yaml: icon

Closed #515. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications

Closed #54491 via #100142. — You are receiving this because you are on a team that was mentioned.

/lifecycle frozen — You are receiving this because you are on a team that was mentioned. Reply to

If anyone still has this issue like me I found a solution, I think it's an issue with the parsing

as a note for others who are looking for an option to do this, there is now a tool to achieve this,