Avoid image builders to hang on registry port 443

[nicolaferraro]

This adds a mapping for the 443 port on the registry, because image publishers, in case of insecure registries, first try to contact port 443, then fallback on port 80.

But if port 443 is not mapped to the container (even on a closed port of the container, as in this case), then the application remains stuck until a timeout occurs. This in the end leads to really slow times for publishing an image.

This is happening e.g. in GoogleContainerTools/kaniko#1013

[k8s-ci-robot]

Welcome @nicolaferraro!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @nicolaferraro. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nicolaferraro
To complete the pull request process, please assign medyagh
You can assign the PR to them by writing /assign @medyagh in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[minikube-bot]

Can one of the admins verify this patch?

[codecov-commenter]

Codecov Report

Merging #8208 into master will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #8208      +/-   ##
==========================================
- Coverage   34.60%   34.59%   -0.02%     
==========================================
  Files         147      147              
  Lines        9378     9381       +3     
==========================================
  Hits         3245     3245              
- Misses       5736     5739       +3     
  Partials      397      397              

Impacted Files	Coverage Δ
cmd/minikube/cmd/node_start.go	9.37% <0.00%> (-0.63%)	⬇️
cmd/minikube/cmd/node_stop.go	13.33% <0.00%> (-0.96%)	⬇️

[medyagh]

thank you for fixing this, do u mind sharing the output that this fixes it ?