Skip to content
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

kubectl configure clarification #166

Merged
merged 2 commits into from
Apr 10, 2023
Merged

Conversation

Franr
Copy link
Contributor

@Franr Franr commented Apr 4, 2023

What?

Clarify a key step required to use the kubectl command.

Why?

To avoid confusion.

References

binbashar/leverage#126

@Franr Franr requested a review from a team as a code owner April 4, 2023 15:32
Copy link
Contributor

@juanmatias juanmatias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added comment

docs/user-guide/leverage-cli/reference/kubectl.md Outdated Show resolved Hide resolved
Co-authored-by: Juan Matías Kungfoo de la Cámara Beovide <[email protected]>
@Franr Franr requested a review from juanmatias April 6, 2023 15:26
@Franr Franr self-assigned this Apr 6, 2023
@Franr Franr added the documentation Improvements or additions to documentation label Apr 6, 2023
@Franr Franr merged commit bf018e8 into master Apr 10, 2023
@Franr Franr deleted the kubectl-configure-clarification branch April 10, 2023 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants