Bug: exec /manager: exec format error after upgrade to 2.0.0

[rvanlaak]

After having upgraded to 2.0.0 through the Helm chart, the new sm-operator-control-manager pod does not start and result in the following logs:

exec /manager: exec format error

My K8S env is running on an ARM architecture, which was not a problem before at all.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-33366
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-33366

[sshadminBW]

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks

[rvanlaak]

I've followed the process as described on https://bitwarden.com/help/secrets-manager-kubernetes-operator/#add-the-repository-to-helm to upgrade the operator from 0.1.0 to 2.0.1

Also, I've tried 'upgrading' the release to any of the other chart versions, like 1.0.0 or 1.1.0 or 2.0.0, but for none of these versions the sm-operator-controller-manager pod seems to output something different as above.

[rvanlaak]

@sshadminBW any news? Would be great to get back ARM-support on the Operator again.

[rvanlaak]

@justindbaur you'd be able to confirm / provide updates on 2.x not being ARM compatible?

[tangowithfoxtrot]

@rvanlaak, thanks for reporting this. I looked into it and it appears to be an issue with the build and release workflows. We're still building ARM variants and they're being pushed to the dev tags, but the release workflow is only pushing the amd64 image variant because it's defaulting to what matches the GH Runner type. ARM support was not intentionally removed.

[rvanlaak]

Thanks for the analysis. Planning on fixes, and anything I can help with?

[tangowithfoxtrot]

We actually were able to push the ARM versions of the operator today, so you should be able to do a fresh pull of the 2.0.0 tag and it should work :)

[rvanlaak]

Just attempted updating to v2.0.1 of the chart and the release app to v2.0.0 , but still get the same error on the container's output:

exec /manager: exec format error

In other words, it does seem that an image is available for the architecture, but something else is going on.

What can I do to provide additional context to this issue?