We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
It proved useful in the latest incident to have the apiserver logs, which I didn't know how to retrieve before. But you can do it:
kubectl proxy & curl -O http://localhost:8001/logs/kube-apiserver.log kill %%
we should include this command in the sre guide when we suspect the master is having a problem.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It proved useful in the latest incident to have the apiserver logs, which I didn't know how to retrieve before. But you can do it:
we should include this command in the sre guide when we suspect the master is having a problem.
The text was updated successfully, but these errors were encountered: