feat(cli): design Cobra plugin entryway file structure mapping doctor…

[Stewartsson]

What does this PR do?

This PR initiates the core architectural foundations for the K8s-native kubectl-kerno plugin extension under Issue #23. It introduces a lightweight, high-performance Go Cobra CLI configuration gateway (cmd/kubectl-kerno/main.go) that structures required query validation flags (--node, --pod, --all-nodes, --output json). It adheres strictly to Krew best practices by initializing dynamic namespace mapping hooks and embedded cloud infrastructure authentication handlers.

Related issue

Closes #23

Checklist

• Engineered modular Cobra CLI plugin entryway file structures mapping doctor command flags
• Integrated k8s auth plugins package layout handlers to fulfill Krew compliance matrices
• Configured semantic verification conditional blocks to isolate target pod context inputs
• All updated typescript/Go scripts explicitly conform to strict POSIX trailing empty row formatting constraints
• ⭐ I have starred this repository!

[github-actions]

🚀 First PR — welcome aboard!

A few things to expect:

1. CI: every PR runs build + race tests + lint + (eventually) the kernel matrix. If something fails, the log will tell you exactly which gate.
2. DCO: every commit needs Signed-off-by: — git commit -s adds it automatically.
3. Conventional Commits: PR titles like feat(doctor): add new rule or fix(bpf): handle X. We squash-merge by default.
4. Review: a maintainer will review within 72 hours. Suggestions are conversations, not orders — push back if something doesn't fit your context.

If you get stuck, reply here or jump to Discussions. We want this PR to land.

[Stewartsson]

Hi Mentor @btushivam! I have successfully engineered and finalized the complete production-grade implementation for the K8s-native kubectl-kerno plugin under Issue #23.

I have pushed three comprehensive architectural layers to fully satisfy all acceptance criteria:

1. Cobra CLI Gateway: Built cmd/kubectl-kerno/main.go to parse validation flags (--node, --pod, --all-nodes, --output json) and handle Krew prefix best practices.
2. Connection Logic: Developed internal/kubectl/exec.go leveraging client-go remotecommand execution and SPDY protocol transports to dynamically stream telemetry back from matching DaemonSet pod contexts.
3. Distribution Manifest: Authored a valid schema-compliant Krew plugin manifest spec descriptor under deploy/krew/kerno.yaml to ensure seamless kubectl krew install integration.

All scripts explicitly conform to strict POSIX formatting guidelines. Ready for final evaluation and merge! 🚀

[Stewartsson]

@btwshivam check for any error if so say i will clear it

[Stewartsson]

@btwshivam check for any error if so say i will clear it