Skip to content

publish to public.ecr.aws #108

Description

@larhauga

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions