New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add example with init container fetching context for non-GCS remote contexts #121

Open
r2d4 opened this Issue Apr 18, 2018 · 4 comments

Comments

Projects
None yet
6 participants
@r2d4
Member

r2d4 commented Apr 18, 2018

Kaniko can work without needing to fetch the remote context itself. This would open the workflow to non-GCS remote contexts.

  1. Init container with with whatever auth helpers needed (gcloud, aws-cli) and credentials mounted in. Downloads context to shared volume
  2. Kaniko container reads locally downloaded context

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?)

@AkihiroSuda

This comment has been minimized.

AkihiroSuda commented Apr 19, 2018

https://github.com/graymeta/stow seems providing abstract interface for GCS, S3, Azure storage, Swift, and Oracle storage.

@alexellis

This comment has been minimized.

alexellis commented Jul 18, 2018

Hi @r2d4 I would be interested in this feature for using Minio or similar within a hybrid/on-premise solution.

Would fetching from a Git repo over SSH/HTTPs be within scope?

Alex

@priyawadhwa

This comment has been minimized.

Member

priyawadhwa commented Jul 19, 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!

@alexellis

This comment has been minimized.

alexellis commented Jul 19, 2018

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.

Alex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment