Jann Fischer
Jann Fischer
Hey, I think the discussion here might have missed an important point. As far as I understood, the request is about matching a top-level group like `tekton.dev` against a pattern...
Fixing this issue should not change current behavior (i.e. `*.tekton.dev` should not match `tekton.dev` by default). I think we might want to write a custom matcher that will match `**.tekton.dev`...
Does this bug actually have impact, or is it just cosmetics? IIRC, when using a digest, the container engine will ignore whatever is specified in the tag.
You could probably also just configure the `aws` CLI to read/write configuration in a different location by setting the `AWS_CONFIG_FILE` environment to point to a read-write filesystem in the container,...
To properly fix this, we might want to have an `emptyDir` mount for `/app/.aws` in the installation manifests.