Update to build and push multi-arch manifests

[jeefy]

This allows us to publish v2.2 registry manifests allowing end-users to consume a single container image rather than specifying their architecture. This will directly address and resolve several issues (including #3137 and #2811)

Example:
docker pull kubernetes-dashboard
Instead of
docker pull kubernetes-dashbaord-amd64

• Update travis-ci.yml to use a newer version of Docker
• Update build/Dockerfile to use a newer version of Docker
• pushToDocker now creates and pushes manifests

Tested and verified on both Docker Hub and GCR (Only had access to a private repo sorry)

If/When this is accepted, there will be additional work updating other repos and documentation to use the Manifest image (kubernetes-dashboard) instead of individual images (kubernetes-dashboard-amd64)

Any questions or comments are appreciated!

[codecov]

Codecov Report

Merging #3143 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3143      +/-   ##
==========================================
+ Coverage      48%   48.02%   +0.02%     
==========================================
  Files         165      165              
  Lines        7960     7960              
  Branches       24       24              
==========================================
+ Hits         3821     3823       +2     
+ Misses       3885     3882       -3     
- Partials      254      255       +1

Impacted Files	Coverage Δ
...p/backend/integration/metric/common/aggregation.go	89.09% <0%> (-1.82%)	⬇️
src/app/backend/sync/secret.go	73.26% <0%> (+2.97%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f51ac63...6120951. Read the comment docs.

[jeefy]

/assign @PeWu

[austbot]

Can you pull the install docker and go into some shell script files and then run them in docker file or Travis that way?

[floreks]

I have one concern regarding this change. As it requires edge docker client with manually enabled experimental flag, it might be a problem for users to use this instead of the current installation methods. At first, we should keep it only as an addition to current deployment methods and not make it the default.

[jeefy]

It only requires the experimental flag to push a manifest to a registry.

Pulling is supported in the stable version of Docker (and has been for some time, early 2017 I believe)

You could pull jeefy/kubernetes-dashboard and it will pull the correct image based on your arch.

On the SIG call today, we decided to hold this back from the next release and look to merge it in after.

[floreks]

Great, if this will work without additional changes to docker then I am ok with it.

[jeefy]

/hold

Awesome! I think we're waiting till after the next release to merge this in.

Once the angular migration is done we can merge this and update everything surrounding it in future PRs.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jeefy]

/remove-lifecycle stale

[maciaszczykm]

Once the angular migration is done we can merge this and update everything surrounding it in future PRs.

@jeefy Are we planning to something about it?

[jeefy]

I'd like to get this in the next release, yes. I want to revisit this once metrics server support is solid.

…

On Thu, Jan 3, 2019 at 10:03 AM Marcin Maciaszczyk ***@***.***> wrote: Once the angular migration is done we can merge this and update everything surrounding it in future PRs. @jeefy <https://github.com/jeefy> Are we planning to something about it? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3143 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABVHeAWfx1AU3WBotE9aVSJEYhheuiqeks5u_hvIgaJpZM4VQbg6> .

[jeefy]

@floreks @maciaszczykm PTAL, I think it's in a good place.

[jeefy]

/hold cancel

[maciaszczykm]

@jeefy Can you solve conflicts?

[mkumatag]

what else pending part of this pr? can we merge this?

[maciaszczykm]

@mkumatag Nothing :)

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jeefy, maciaszczykm

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 [jeefy,maciaszczykm]

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