What would you like to be added:
Today, the other falco projects are published to public.ecr.aws. We would like the k8s-metacollector to be published as well.
Why is this needed:
This would make it consistent with the other projects, and ensure that we can pin on the aws registry, which can have performance and cost optimization benefits when falco is deployed in AWS.
Example of workflow used in falcosidekick: https://github.com/falcosecurity/falcosidekick/blob/master/.github/workflows/push-main.yml#L64-L83
What would you like to be added:
Today, the other falco projects are published to public.ecr.aws. We would like the
k8s-metacollectorto be published as well.Why is this needed:
This would make it consistent with the other projects, and ensure that we can pin on the aws registry, which can have performance and cost optimization benefits when falco is deployed in AWS.
Example of workflow used in falcosidekick: https://github.com/falcosecurity/falcosidekick/blob/master/.github/workflows/push-main.yml#L64-L83