Dimitris Karakasilis

@richard-cox suggested that we use a custom key for user provided values (e.g. `userValues`). This will allow us to show only those values in the UI so that we don't...

In any case, the operator should decide which values should the user be allowed to change and Epinio should ensure the user can't change anything other than those values. Maybe...

The solution implemented here may also work for this: https://github.com/epinio/epinio/issues/1633#issuecomment-1195054999

I think this issue will be also solved with what is described here: https://github.com/epinio/epinio/issues/593 One would simply have to register to all events using the same event mechanism. Maybe some...

Relevant: https://github.com/epinio/epinio/issues/1295

Can we base this on rootless container so we don't mess up file permission with every build? Podman for example?

The issue is easily reproducible is you go to the `src/jetstream` directory and you run: ``` GOOS=darwin GOARCH=arm64 go build ```

Given a Dockerfile: ``` FROM ubuntu # For GOARCH=arm : #RUN apt update && apt install -y golang gcc-arm-linux-gnueabihf ca-certificates gcc-aarch64-linux-gnu # For GOARCH=arm64: RUN apt update && apt install...

Someone has this solution already implemented here: https://github.com/goreleaser/goreleaser-cross#examples

We've had various hacks to make the communication with the built-in registry encrypted in the past. Even then, there were cases in which the hacks didn't work. Since the internal...