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
apply -f <yaml>
cp <src> <destination>
describe pod <pod>
exec -it <pod> -- /bin/sh -c "cat >> /root/etc/crontab"
exec -it <pod> -- /bin/sh -c <command>
get namespaces
get nodes -o json
get pods -o json
get pods -o wide --sort-by "metadata.creationTimestamp"
get role -o json
get secret <secret> -o json
get secrets -o json
additionally, there is a command that allows for arbitrary kubectl commands.
I see a few paths moving forward.
Use the API. this is far more reliable and forward compatible. most commands in use are data retrieval and trivial to replace. exec is harder. running arbitrary kubectl commands would be impossible without uploading a second binary
Re-execute the peirates binary from within itself. Add a special switch to peirates that interprets the remaining arguments as a kubectl command and passes them directly to kubectl. If this works it will solve our crashing problems.
Hybrid. Choose option 2 for now. replace things with API calls over time when possible to reduce our kubectl usage surface.
The text was updated successfully, but these errors were encountered:
this is almost certainly the cause of #4 , #5 , #6 , #7
this command was never intended to be used as a library and we probably should not have done it.
here are the current usages, including commented out ones
and here are the unique forms of usage:
additionally, there is a command that allows for arbitrary kubectl commands.
I see a few paths moving forward.
exec
is harder. running arbitrary kubectl commands would be impossible without uploading a second binaryThe text was updated successfully, but these errors were encountered: