Add a blog post with a clientcmd tutorial

[skitt]

trafficstars

This adds a blog post giving instructions on how to use clientcmd to handle kubectl-style command-line options in CLI tools.

[netlify[bot]]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	9a77ed1d2339510a214a7d6dfd6e08d216a3c15e
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/673f31c0d953e600080b1bce
😎 Deploy Preview	https://deploy-preview-47263--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sftim]

Thanks. Please hold whilst we find a reviewer.

/hold pending assignment of publication date!

[sftim]

Hi. We're now looking at publication in September 2024.

[sftim]

How about publication on the 26th? Please aim for that.

[sftim]

OK! This needs a tech review next. Either SIG CLI or SIG API Machinery; take your pick.

[skitt]

OK! This needs a tech review next. Either SIG CLI or SIG API Machinery; take your pick.

I vote for SIG CLI.

[skitt]

@sftim is it up to me to request a technical review from SIG CLI?

[sftim]

Hi. The blog team is short on capacity, so reviews are taking a long time. How about we aim for publication on the 2nd of December?

[skitt]

Hi. The blog team is short on capacity, so reviews are taking a long time. How about we aim for publication on the 2nd of December?

OK, I’ve amended the PR accordingly.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Ritikaa96]

As per above discussion, the PR is still waiting for reviews so removing the tag /remove-lifecycle stale

[lmktfy]

If we do publish this, I want to understand who the audience is

• Kubernetes contributors?
• Kubernetes users?
• People writimg kubectl plugins?
• another audience

[skitt]

If we do publish this, I want to understand who the audience is

• Kubernetes contributors?
• Kubernetes users?
• People writimg kubectl plugins?
• another audience

I would say people writing kubectl plugins or any tool designed to interface with the Kubernetes API server. Given the difficulty in getting this reviewed, perhaps it would be a better fit in the kubectl or client-go docs…

[lmktfy]

Sorry about the wait; this is our oldest open PR.

To avoid it getting overlooked, would you be willing to open a new PR and mention this one in the description?

[illume]

I went through the remaining open conversations, and there are only ones open that should be closed.

[skitt]

Sorry about the wait; this is our oldest open PR.

To avoid it getting overlooked, would you be willing to open a new PR and mention this one in the description?

I could, but if a PR for a blog post takes more than a year to be reviewed, it might be an indication that the content isn’t useful or relevant — what do you think?

[k8s-ci-robot]

@illume: changing LGTM is restricted to collaborators

In response to this:

Thanks for this. 🎉

I think it would be great for the ecosystem if there was more knowledge about making kubectl plugins well.

This blog meets the Kubernetes blog guidelines.

The audience is primarily Go developers building command-line clients for Kubernetes, especially those interested in creating tools that behave like kubectl or extend it via plugins.

I tested the full code example, and it works.

mkdir clientcmddemo
cd clientcmddemo
go mod init clientcmddemo
# put full example code from article in main.go
go mod tidy
go get github.com/spf13/pflag
go get k8s.io/client-go@latest
go run main.go --kubeconfig ~/.kube/config

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: illume Once this PR has been reviewed and has the lgtm label, please assign lmktfy for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/blog/OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[illume]

@skitt I'm new around this repo, but I think there's just a lack of blog reviewers.

I'll post it to the sig-docs-blog channel for more visibility.

[skitt]

@skitt I'm new around this repo, but I think there's just a lack of blog reviewers.

I'll post it to the sig-docs-blog channel for more visibility.

Right, that makes sense :wink:. Thanks for all your help here!