Add the CI to build multi-platform container images

[tenzen-y]

Signed-off-by: tenzen-y yuki.iwai.tz@gmail.com

What this PR does / why we need it:
I added the CI to build multi-platform container images using composite action and reusable workflows.
Also, I cleaned up config files for actions according to the below documents.

• https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#inputs
• https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions
• https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1900

Checklist:

• Docs included if any changes are user facing

[coveralls]

Coverage decreased (-0.1%) to 73.431% when pulling f150aad on tenzen-y:add-ci-to-build-multi-arch-image into e02eb6e on kubeflow:master.

[tenzen-y]

Since we face the below error, we can not build multiplatform container images with GPU support.
Once we use AWS self-hosted runner, we will be able to build it.

System.IO.IOException: No space left on device : '/home/runner/runners/2.296.2/_diag/Worker_20220918-065331-utc.log'
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
   at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.Diagnostics.TextWriterTraceListener.Flush()
   at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
   at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
   at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
   at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
   at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
System.IO.IOException: No space left on device : '/home/runner/runners/2.296.2/_diag/Worker_20220918-065331-utc.log'
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
   at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.Diagnostics.TextWriterTraceListener.Flush()
   at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
   at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
   at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
   at GitHub.Runner.Common.Tracing.Error(Exception exception)
   at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.296.2/_diag/Worker_20220918-065331-utc.log'
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
   at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.Diagnostics.TextWriterTraceListener.Flush()
   at System.Diagnostics.TraceSource.Flush()
   at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
   at GitHub.Runner.Common.TraceManager.Dispose()
   at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
   at GitHub.Runner.Common.HostContext.Dispose()
   at GitHub.Runner.Worker.Program.Main(String[] args)

https://github.com/kubeflow/katib/actions/runs/3075994787

[tenzen-y]

Needs to specify string data.

https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_iddefault

[tenzen-y]

type is not available.

https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#inputs

[tenzen-y]

Needs to specify description field.

https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_iddescription

[johnugeorge]

How long does it take in CI now ?

[tenzen-y]

How long does it take in CI now ?

@johnugeorge Maybe, over an hour but I'm not sure about the accurate duration. Would you like to see how long it will take by restarting all jobs?

[tenzen-y]

I have pushed to kick the CI.

[tenzen-y]

@johnugeorge I have checked what it spends about 2 hours for CI since this PR.

So, It might be better to introduce the order to run jobs using needs in another PR so that we can run efficiently jobs.

For example, Lint test -> Unit test -> Build test -> Integration Test.

What do you think?

[johnugeorge]

@tenzen-y How does it help?

[tenzen-y]

@tenzen-y How does it help?

@johnugeorge
Since even in the case of new commits with basic errors such as lint or unit tests, we run all jobs, including integration tests that take a long time, we face a limitation of the number of actions jobs for the katib repo, and then we can not run jobs in other PRs.

Introducing needs, in the case of above, as we don't run jobs for integration tests, we can save the number of job executions.

[johnugeorge]

Sure. Do you want to do it in a separate PR?

[tenzen-y]

Sure. Do you want to do it in a separate PR?

Yes, I would like to create a separate PR to resolve it since I created this PR to resolve #1900.

[johnugeorge]

Ready to merge this?

[tenzen-y]

Ready to merge this?

Yes. Let's merge this!

[johnugeorge]

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johnugeorge, tenzen-y

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [johnugeorge]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment