Micah Nagel
Micah Nagel
@Szymongib / @gabrieljackson If you want to assign me to this, I've got a PR that hopefully resolves - https://github.com/mattermost/mattermost-operator/pull/305 - happy to make any modifications needed to get it...
> I would like to understand the issue more. The way dashboard queries the initial list of charts is by running `helm ls --all-namespaces --output json`. In the results JSON,...
> I would not like to parse raw Helm information from secrets, I'd rather rely on some standard queries via Helm. That's understandable. For clarification though you could use standard...
> While creating PVC by Operator might be useful for people to start quickly, I wonder if it would not be better to just pass PVC name as Local file-store...
Looks like the issue with showing all possible components was resolved in cosign - https://github.com/sigstore/cosign/pull/1872 Running `cosign tree` on images now only returns existing signature/sbom/attestation.
Going to unassign myself and drop a few notes from follow on todos to fully close this issue. With the merged PR cosign artifacts should be fully supported and discoverable...
Also ran into this issue on newer RKE2 versions. It seems linked back to [this commit](https://www.github.com/k3s-io/k3s/commit/c45524e66237bdb491ebb0afc633a5bd6d3a76c8) which introduced the `config_path` line. The containerd update to 1.7.7+ actually did not immediately...
@gabrieljackson that is correct, we just added that service on its own, no other modifications to deployment, etc. We've had this deployed in prod (istio injected with the extra service)...
Just to clarify on flux support - OCIRepository cannot be used as a source for a HelmRelease. So I believe to fully support OCI sourced Flux HelmReleases with Zarf we'll...
Just noting still encountering this on RKE2 with EBS backed PVCs. Not really any additional details on how/why we encountered this but we were able to workaround by pushing the...