https://github.com/brennerm/cdk8s-docker

inofficial Docker image for cdk8s
https://github.com/brennerm/cdk8s-docker

cdk8s kubernetes kubernetes-manifests

Last synced: about 1 month ago
JSON representation

inofficial Docker image for cdk8s

• Host: GitHub
• URL: https://github.com/brennerm/cdk8s-docker
• Owner: brennerm
• Created: 2020-05-10T00:42:15.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-05-11T19:49:00.000Z (over 4 years ago)
• Last Synced: 2024-06-12T18:11:25.345Z (3 months ago)
• Topics: cdk8s, kubernetes, kubernetes-manifests
• Language: Shell
• Homepage:
• Size: 3.91 KB
• Stars: 7
• Watchers: 4
• Forks: 4
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Initializing a new app

Initializing a new app requires you to mount the target directory into the container like so: `docker run -v /my-new-cdk8s-project:/files brennerm/cdk8s init typescript-app`.

## Synthesizing your app

Synthesizing works similar but instead of mounting an empty directory you need to mount the directory containing your cdk8s code. This could look like: `docker run -v /my-existing-cdk8s-project:/files brennerm/cdk8s synth`.

## Synthezising Python code

To be able to synthesize Python cdk8s code you need to use the _brennerm/cdk8s:python_ image. It contains additional dependencies like Python 3.7 and pipenv.

## Setting the owner of generated files

No matter if you are initializing a new app or synthesizing your manifests, all generated files will have a root ownership afterwards. This happens cause cdk8s is being executed as root to be able to read and write files from and to the volume due to [this issue](https://github.com/moby/moby/issues/2259). To fix this you can pass the `-u uid=$(id -u)` parameter to the `docker run command`. Tried to prevent executing as root but currently it does not seem possible while keeping a good user experience of the resulting image.