cdk8s dasm: convert a yaml manifest to a cdk8s chart
See original GitHub issueWe propose a new command called cdk8s dasm
that will take a k8s yaml as input and will generate code (in one of the supported programming languages) which will synthesize the same manifest output (as much as possible).
It’s nice way to migrate from manifests to cdk8s.
See the cdk-dasm as an example.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:40
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Chart - cdk8s
The Chart is a container that synthesizes a single Kubernetes manifest. ... (recursively) and emit a single YAML manifest that includes all these...
Read more >How does it work? - cdk8s
Each chart is synthesized into a separate Kubernetes manifest file. Charts are, in turn, composed of any number of constructs, and eventually from...
Read more >TypeScript - cdk8s
Use this construct to import an existing Helm chart and incorporate it into ... Reads a YAML manifest from a file or a...
Read more >Java - cdk8s
Otherwise, a name will be generated by calling Chart.of(this). ... Type: java.lang.String. Local file path or URL which includes a Kubernetes YAML manifest....
Read more >synth - cdk8s
The properties of the synthesized YAML from cdk8s synth can be modified by the ... You can perform validation on the manifests produced...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@moises-perez-tfs We still don’t have a concrete plan for this feature. Noted that it would be good to have it available via an API as well 😃
I was exploring to find a feature like this. Our use case is to automate the management (add, remove) of Identity Mappings in the aws-auth ConfigMap in EKS. Is this feature also going to be available in code (not just command) to enable automation?