Support opa-envoy linux/arm64 Docker Image

[Nebu1eto]

What is the underlying problem you're trying to solve?

I'm using opa-envoy, but it doesn't support linux/arm64 architecture. So I can't use this on Graviton 2 (AWS).

Describe the ideal solution

If there are no problem to build opa-envoy image for arm64, can you please support this? If not, It is issue and it have to be resolved.

[srenatus]

There's no technical reason not to do it; it's just work that needs to be done. Would you be interested in adding the steps done with OPA in db4d987 with opa-envoy-plugin...?

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days.

[sidharthramesh]

can we please have this?

[srenatus]

Contributions welcome! Happy to assist.

The setup here could also be simpler than what OPA does: since no cgo is needed, we could use ko.

[sidharthramesh]

Thank you @srenatus. I'll get started on this. CC: @Areefks

[sidharthramesh]

@srenatus Ko seems to do all of the heavy lifting of multiarch image builds. Should I replace all of these lines with Ko's CLI instead of docker build?

https://github.com/open-policy-agent/opa-envoy-plugin/blob/c37ea9d489b8f8144d449abbe294a1d6cde7ffa2/Makefile#L86-L111

[sidharthramesh]

@srenatus Do we need the whole replacing the Dockerfile arch business when we switch to Ko?

sed -e 's/GOARCH/$(GOARCH)/g' Dockerfile > .Dockerfile_$(GOARCH)

[sidharthramesh]

Where exactly is the docker build happening?

https://github.com/open-policy-agent/opa-envoy-plugin/blob/c37ea9d489b8f8144d449abbe294a1d6cde7ffa2/.github/workflows/post-tag.yaml#L23 this doesn't seem to be building the images, only the binaries?

[srenatus]

https://github.com/open-policy-agent/opa/blob/main/.github/workflows/post-merge.yaml#L160 should do it, at least the -edge images.

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days.

[3goats]

+1

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.

[leofernandezg]

+1

[kenissongmelo]

+1

[leandrosantoro]

+1

[tjons]

@srenatus I'll work on this one!

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.

[tjons]

open-policy-agent/opa-envoy-plugin#577 should resolve this!

[srenatus]

🥳 yaaaay