[ QUESTION ] can kubectl diff display pruned resources after apply the yaml file?

[saniyar-dev]

What would you like to be added:
Hi, It would be great that we can see the resources that are going to be used before/without applying a yaml file. This feature could be very useful on strategic decisions on how we need to grow the cluster size or what resources should we purchase without making a big margin at a Paas provider company.

Why is this needed:
In my usecase i need it to decide that we need to purchase what kind of resources for the k8s cluster, but in many other usecases it can be helpful too, for example you can think of it as a checker for a large paas company which provides a managed k8s cluster for convenient use for people who don't know kubernetes or don't want to manage their own cluster, so people can use this checker before deploying their application and knowing that their applications/pods are going to be running or not, before creating any critical decision.

Also i saw this block on the official documentation which quotes:

The working group is still busy trying to improve some of these things:

• Server-side apply is trying to improve the apply scenario, by adding owner semantics to fields! It's also going to improve support for CRDs and unions!
• Some kubectl apply features are missing from diff and could be useful, like the ability to filter by label, or to display pruned resources.
• Eventually, kubectl diff will use server-side apply!

[EDIT] Documentation link is here!

So as it's mentioned on the documentation i think that its also on the enhancement roadmap.

I would love to be part of the implementation of such great feature, but don't know where to start can anyone help?

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[Aaina26]

hi! this enhacement is being tracked here: kubernetes/enhancements#3659

[mpuckett159]

/close
Since this is already part of the design roadmap for server side apply and prune I'm going to close this but thank you for the plus one on the roadmap.

[k8s-ci-robot]

@mpuckett159: Closing this issue.

In response to this:

/close
Since this is already part of the design roadmap for server side apply and prune I'm going to close this but thank you for the plus one on the roadmap.

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.