UI: make it hard to miss Important notices

[medyagh]

I noticed many ppl miss the notice to use different Port for Mac Os for registry addon

$ minikube addons enable registry
💡  Registry addon on with docker uses 55012 please use that instead of default 5000
📘  For more information see: https://minikube.sigs.k8s.io/docs/drivers/docker
    ▪ Using image registry:2.7.1
    ▪ Using image gcr.io/google_containers/kube-registry-proxy:0.4
🔎  Verifying registry addon...
🌟  The 'registry' addon is enabled

maybe we can have a new style that creates a Index Pointer Emoji in a Box with one line empty above and bellow so it is hard to miss

$ minikube addons enable registry
👉  ------------------------------------------------------------------------------------------
👉   Registry addon on with docker uses 55012 please use that instead of default 5000.   
👉  ------------------------------------------------------------------------------------------
📘  For more information see: https://minikube.sigs.k8s.io/docs/drivers/docker
    ▪ Using image registry:2.7.1
    ▪ Using image gcr.io/google_containers/kube-registry-proxy:0.4
🔎  Verifying registry addon...
🌟  The 'registry' addon is enabled

[sharifelgamal]

I support making important notes more obvious, but just as an aside, the sentence "Registry addon on with docker uses 55012 please use that instead of default 5000." is wildly unclear. 5000 of what?

[afbjorklund]

I support making important notes more obvious, but just as an aside, the sentence "Registry addon on with docker uses 55012 please use that instead of default 5000." is wildly unclear. 5000 of what?

It should probably at least say "port 5000", maybe even give an example.

https://docs.docker.com/registry/deploying/

[afbjorklund]

a Box with one line empty above and bellow so it is hard to miss

Or you could go to town and use: https://github.com/Delta456/box-cli-maker

MINIKUBE_IN_STYLE=true

    ╭──────────────────────────────────────────────────────────────────────────────────────────╮
💡  │Registry addon on with docker uses port 49170 please use that instead of default port 5000│
    │                                                                                          │
    ╰──────────────────────────────────────────────────────────────────────────────────────────╯
📘  For more information see: https://minikube.sigs.k8s.io/docs/drivers/docker
    ▪ Using image registry:2.7.1
    ▪ Using image gcr.io/google_containers/kube-registry-proxy:0.4
🔎  Verifying registry addon...
🌟  The 'registry' addon is enabled

MINIKUBE_IN_STYLE=false

  ╭──────────────────────────────────────────────────────────────────────────────────────────╮
* │Registry addon on with docker uses port 49170 please use that instead of default port 5000│
  │                                                                                          │
  ╰──────────────────────────────────────────────────────────────────────────────────────────╯
* For more information see: https://minikube.sigs.k8s.io/docs/drivers/docker
  - Using image registry:2.7.1
  - Using image gcr.io/google_containers/kube-registry-proxy:0.4
* Verifying registry addon...
* The 'registry' addon is enabled

EDIT: I added the missing "port" and "driver", there was an extra "on" in the sentence as well

See 5cf8dce#diff-674f8712fba78241aab11240ee7ca41ccfb04fc933ac5fcf9da37f0256e5adc7

[afbjorklund]

Even more aside, this "insecure registry" hack with localhost:5000 is getting old...

One of these days, we would have to deploy a real registry with real certificates ?

https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry

See #10780 (comment)

Until then, there is minikube image for all your container runtime image needs.

That will use ssh to talk to the nodes, so it doesn't need this http-on-port-5000 hack.

[medyagh]

@afbjorklund I like the box idea, we could add it for the Exit with Advcice too

for example in this UI, it is easy to miss the "Suggestion" without a box

$ make && mk start --driver=docker
go build  -tags "" -ldflags="-X k8s.io/minikube/pkg/version.version=v1.18.1 -X k8s.io/minikube/pkg/version.isoVersion=v1.18.0-1615350772-10704 -X k8s.io/minikube/pkg/version.gitCommitID="ff0e25ada888cf1bd7b262857ce96531c1231e69-dirty" -X k8s.io/minikube/pkg/version.storageProvisionerVersion=v4" -o out/minikube k8s.io/minikube/cmd/minikube
😄  minikube v1.18.1 on Darwin 11.2.3
✨  Using the docker driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=2, Memory=4000MB) ...
✋  Stopping node "minikube"  ...
🛑  Powering off "minikube" via SSH ...
🔥  Deleting "minikube" in docker ...
🤦  StartHost failed, but will try again: creating host: create: creating: prepare kic ssh: copying pub key: docker copy /var/folders/s8/wxxccj3x7mncysv_zzm5w_r400h78j/T/tmpf-memory-asset265183811 into minikube:/home/docker/.ssh/authorized_keys, output: lstat /private/var/folders/s8/wxxccj3x7mncysv_zzm5w_r400h78j/T/tmpf-memory-asset265183811: no such file or directory
: exit status 1
🔥  Creating docker container (CPUs=2, Memory=4000MB) ...
😿  Failed to start docker container. Running "minikube delete" may fix it: creating host: create: creating: prepare kic ssh: copying pub key: docker copy /var/folders/s8/wxxccj3x7mncysv_zzm5w_r400h78j/T/tmpf-memory-asset091998406 into minikube:/home/docker/.ssh/authorized_keys, output: lstat /private/var/folders/s8/wxxccj3x7mncysv_zzm5w_r400h78j/T/tmpf-memory-asset091998406: no such file or directory
: exit status 1

❌  Exiting due to GUEST_KIC_CP_PUBKEY: Failed to start host: creating host: create: creating: prepare kic ssh: copying pub key: docker copy /var/folders/s8/wxxccj3x7mncysv_zzm5w_r400h78j/T/tmpf-memory-asset091998406 into minikube:/home/docker/.ssh/authorized_keys, output: lstat /private/var/folders/s8/wxxccj3x7mncysv_zzm5w_r400h78j/T/tmpf-memory-asset091998406: no such file or directory
: exit status 1
💡  Suggestion: Ensure the tmp directory path is writable to the current user.
🍿  Related issue: https://github.com/kubernetes/minikube/issues/10772