Tirumarai Selvan

It is either an HTTP call or aws cli. Either way it breaks the current pattern and proves an exception (till now). If we come up with some other registry...

@nizar-m Yes, but that is clearly out of the scope of gitkube.

@ssiddhantsharma Yes! Basically, currently gitkube is installed via kubernetes manifest files. Same for remotes. We have a gitkube cli tool to do the same work. We should have tests which...

Yeah, I suppose there will be a problem with really long `ns + remote` names. Good catch. Maybe we can use some hash to represent (the user and groups) internally....

I think it will be a nice add-on to give a test docker registry in-built. Although, the user may still need to configure persistent volume for the registry. So the...

@pdomagala Do you mean not specifying a remote docker registry? If so, that means it would work only for a single node cluster.

Yes, this issue is to make available arbitrary params to the build environment which can then be used in custom hooks. Custom hooks is in a WIP branch although I...

@jsierles docker build args support is here https://github.com/hasura/gitkube/pull/64

Hey @dlorenc Very interesting. We should definitely talk! You can reach out to me at tiru{AT}hasura.io

@dsandip Will you please add the docs/gke.md ?