Skip to content
This repository has been archived by the owner on Nov 11, 2024. It is now read-only.

Support exporting resources from kam #62

Open
gnunn1 opened this issue Oct 13, 2020 · 1 comment
Open

Support exporting resources from kam #62

gnunn1 opened this issue Oct 13, 2020 · 1 comment
Labels
kind/enhancement New feature or request

Comments

@gnunn1
Copy link

gnunn1 commented Oct 13, 2020

Is your feature request related to a problem? Please describe.
kubectl and oc have deprecated and removed the --export option. In OpenShift it's common to use tools like oc new-app or odo to bootstrap an application. However when you want to GitOps the application you need to export those resources and remove all of the cruft (managedFields, status, etc) from the result.

It would be nice if kam could handle exporting resources and even nicer if kam could do it based on the schema for the selected object to export only the relevant fields.

Describe the solution you'd like
Exporting to pure yaml at a minimum would be very useful but being able to bootstrap resources to a kustomize base or a helm chart would be totally awesome as well.

Describe alternatives you've considered
Using a bash script which pipes the resource through yq to strip unneeded fields.

@amitkrout amitkrout removed their assignment Oct 19, 2020
@bigkevmcd
Copy link
Contributor

We could consider how https://github.com/itaysk/kubectl-neat works (which is a plugin for kubectl to do this).

@bigkevmcd bigkevmcd added the kind/enhancement New feature or request label Feb 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants