Jason Hall

> Btw. as far as I understand the permission concept in k8s a user can either see all secrets in a namespace or none. If you want to hide resources...

> The controller looks for secret refs in volumes and env and also for CSI volumes referencing secrets. It saves the information in form of the names of environment variables...

> Btw I am clueless what the problem of that pipeline is. That error is just (badly) telling you you need to `gofmt` that file. You can do that with...

That error typically means that the image was built for a different architecture than the one it's running on. In this case, the image currently defined in `docker-build` is `docker.io/library/docker:stable@sha256:18ff92d3d31725b53fa6633d60bed323effb6d5d4588be7b547078d384e0d4bf`...

This sounds like another issue, possibly related to https://github.com/tektoncd/catalog/issues/628

(1) sounds generally better to me, but it makes the examples a bit less useful since you can't copy/paste them without doing the build yourself. I'm not sure (2) solves...

The `ko` codebase has made some changes recently to make it more easily consumable as a library by other Go programs, mainly to support Skaffold (see https://github.com/google/ko/pull/348). This should also...

I wouldn't say "replace", since `ko` can't do some of the things Docker can, if you specify a Dockerfile. But it could be a useful simplification/optimization if your Dockerfile is...

> ah that makes sense @bwagner5 , thanks for sharing. > > What we need to figure out now is how to use KO as a library instead of a...

> nice, thanks for sharing @imjasonh ! > > > > Is there a good/supported/preferred way to provide the go binary "already built"? There isn't. ko makes some assumptions about...