Three Dockerfiles in repo could be a single about nfs-ganesha-server-and-external-provisioner

[consideRatio]

@kmova or @kvaps I'd love to help with this, but while I think the goal is clear - to not maintain separate arm64/amd64 Dockerfiles, it isn't obvious how to go about this.

I note that the only file referencing the deploy/docker/arm and deploy/docker/x86_64 folders is the Makefile. I note that the Makefile has commands specifically for arm but not for x86_64/amd64, providing some assisting commands to build an arm image in an amd64 environment using CPU architecture emulation.

I believe I don't have the full picture of this setup in general, and don't know how to proceed in order to refactor away on Dockerfile. I guess a small intervention would be to let the deploy/docker/arm become a symlink to deploy/docker/x86_64 as a starting point though.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[consideRatio]

/remove-lifecycle stale