build Prow image in automation

[medyagh]

What Happened?

we have an image that lets users run minikube inside a container,
the image is used here https://github.com/kubernetes/test-infra/blob/f648d5a9cc8b9abdc6a196d1d1c9df0f4ee1f89a/config/jobs/kubernetes/minikube/minikube.yaml#L26

and we need to create a github action to push it to Docker hub (so it gets updates from the OS)
https://github.com/kubernetes/minikube/tree/master/deploy/prow

Attach the log file

n/a

Operating System

None

Driver

None

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten