Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add example with init container fetching context for non-GCS remote contexts #121
Kaniko can work without needing to fetch the remote context itself. This would open the workflow to non-GCS remote contexts.
Alternatively, we could just target the S3 compatible API, which is supported by GCP and AWS. We'd need a more generic way of getting passing credentials (I think?)
referenced this issue
Jul 7, 2018
Hey @alexellis , I think that would be within scope since Docker allows for Github repos as build contexts.
Could you open a separate issue for this? It'll be easier to keep track of, and if you're interested in contributing this feature I can provide more details!
This is how I did it via a Gist + init container. https://gist.github.com/alexellis/87d732a4b5fe056f5bf903aa6e6437ed
It'd be far cleaner within kaniko - I'd also be interested in some details, but am unsure if I can commit to contribute it until I get CLA approved and can size the work.