kubectl diff does not work with applysets

[uhthomas]

What happened:

❯ KUBECTL_APPLYSET=true kubectl diff --applyset=applyset/automata -f bazel-out/k8-fastbuild/bin/k8s/unwind/list.json --prune
error: unknown flag: --applyset
See 'kubectl diff -h' for help and example

What you expected to happen:

kubectl should show a diff of what changes would be made.

How to reproduce it (as minimally and precisely as possible):

See above.

Anything else we need to know?:

ApplySets were introduced recently, I would have expected them to work with diff also.

https://kubernetes.io/blog/2023/05/09/introducing-kubectl-applyset-pruning/

Environment:

• Kubernetes client and server versions (use kubectl version): v.127.2
• Cloud provider or hardware configuration: N/A
• OS (e.g: cat /etc/os-release): N/A

[mpuckett159]

/triage accepted
Alpha versions of features are not guaranteed to be fully feature, though if someone would be willing to add this feature we would accept a PR for it.

[varshaprasad96]

@mpuckett159 @uhthomas I can look into this. Looking to get familiar with the code base, and could start with this.
/assign

[kimchidonut0]

Hi there @mpuckett159, is this issue still up for grabs? If so, I'd happily look into it.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

[SanjayVas]

/remove-lifecycle stale

This is a missing piece of the KEP-3659 implementation, and is specifically covered in the "Required for MVP release" section.