Generate Helm Charts from Kubernetes api objects
This will be a stand-alone fork from appscode/chartify
go get -u github.com/jpdasma/chartify-ng
You can provide Kubernetes objects as YAML/JSON files in a directory using --kube-dir flag. Or, you can read Kubernetes objects from a cluster. Chartify will read objects from the current context of your local kubeconfig file.
You can use this as a standalone cli.
chartify-ng create NAME [FLAGS]
--chart-dir string Specify the location where charts will be created (default "charts")
--configmaps stringSlice Specify the names of configmaps(configmap@namespace) to include in chart
--daemons stringSlice Specify the names of daemons(daemon@namespace) to include in chart
--deployments stringSlice Specify the names of deployments(deployments@namespace) to include in chart
--jobs stringSlice Specify the names of jobs(job@namespace) to include in chart
--kube-dir string Specify the directory of the yaml files for Kubernetes objects
--namespace string Specify the namespace where the resources will be fetched
--pods stringSlice Specify the names of pods(pod@namespace) to include in chart
--pvcs stringSlice Specify the names of persistent volume claims(pvc@namespace) to include in chart
--pvs stringSlice Specify the names of persistent volumes(pv@namespace) to include in chart
--rcs stringSlice Specify the names of replication cotrollers(rc@namespace) to include in chart
--replicasets stringSlice Specify the names of replica sets(rs@namespace) to include in chart
--secrets stringSlice Specify the names of secrets(secret@namespace) to include in chart
--services stringSlice Specify the names of services(service@namespace) to include in chart
--statefulsets stringSlice Specify the names of statefulsets(statefulset@namespace) to include in chart
--storageclasses stringSlice Specify the names of storageclasses(storageclass@namespace) to include in chart
--preserve-name bool Specify if you want to preserve resources name from input yaml true/false (default: false)
Please file an issue if you think you've found a bug. Be sure to describe
- How can it be reproduced?
- What did you expect?
- What actually occurred?
- Kubernetes version, Helm version, Go version, platform, etc. if possibly relevant.
- Update conventions followed by modern charts
- Support new api versions
- Act as helm plugin