-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
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
docs: explain minikube detection #6512
docs: explain minikube detection #6512
Conversation
Also explaining how to find current context as many k8s newbies might not know this. It's also worth debating calling this term "kubectl context" instead of "kubernetes context", as Kubernetes does not have this notion, only kubectl does. Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Codecov Report
@@ Coverage Diff @@
## main #6512 +/- ##
==========================================
+ Coverage 70.43% 70.45% +0.01%
==========================================
Files 515 515
Lines 23127 23142 +15
==========================================
+ Hits 16289 16304 +15
- Misses 5780 5782 +2
+ Partials 1058 1056 -2
Continue to review full report at Codecov.
|
Please visit http://34.94.56.85:1313 to view changes to the docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Fixes: #4701
Description
Also explaining how to find current context as many k8s newbies might not know
this. It's also worth debating calling this term "kubectl context" instead of
"kubernetes context", as Kubernetes does not have this notion, only kubectl
does.
User facing changes (remove if N/A)
Started using
<sup>
tag which rendered larger than the main body font.