Andreas Kupries

The mountpoints are created from go code, i.e. the API server ... The names are derived / the same as the configuration name. For configurations derived from a service we...

I was mistaken. The go code simply passes the names of the configurations into the app chart, as `[]string`, and the chart then uses these for the volumes (names, and...

Spec: - Keep existing field `configurations` of type `[]string`, for compatibility. - Add new field `configpaths` of type `[]struct { name : string, path : string }`. Old standard app...

The single failure is a plain push with custom secret - Different from first run, test for overcoming a bad staging. I suspect that these are transient network and cluster...

Technically yes. Practically I do not see us working on it until it becomes absolutely necessary by something else. Closing.

https://goreleaser.com/customization/docker_sign/#signing-docker-images-and-manifests > Assuming you have a `cosign.key` in the repository root and a `COSIGN_PWD` environment variable, the simplest configuration to sign both Docker images and manifests would look like this:...

On `cosign`: https://docs.sigstore.dev/cosign/installation/ and https://docs.sigstore.dev/cosign/key-generation

### Research Status Rancher processes UI logout requests in `pkg/auth/tokens`. The existing code removes the relevant cookies from the browser and deletes the Rancher Token resource associated with the current...

I believe from that text that @kwwii is ok with the backend taking a general filter clause which can do more than just filtering by groups. He simply does not...

Hello @braunsonm. This is one of the tickets we decided to close in our last session triaging the icebox/backlog. It was closed because we do not see us addressing it...