fix windows packing installer alert: unknown publisher

[Ehud-Banunu]

The exact command to reproduce the issue:
From the listing at https://github.com/kubernetes/minikube/releases ,
on Windows10 Home, attempt to install v1.7.3 or v1.7.2 -
either minikube-windows-amd64.exe or minikube-installer.exe

The full output of the command that failed:

The output of the minikube logs command:

N/A

The operating system version:
Windows10 Home

[blueelvis]

Hi!

Thanks for reporting this issue. Could you please click on More Info? Once you do, you should see an option to Run Anyway like below -

Kindly click on it and the installation should start. This would work for the installer.

If you just want to use the minikube-windows-amd64.exe, please unblock the file by following the procedure over here - https://mywindowshub.com/how-to-unblock-a-file-in-windows-10/

[afbjorklund]

This seems to be just as annoying as the Mac Gatekeeper "feature".

So now also the Win binaries needs to be signed (somehow), I guess ?

https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-smartscreen-extended-validation-ev-code-signing-certificates/

@tstromberg : maybe we can offload this to e.g. chocolatey by default ?

[Ehud-Banunu]

Thanks for the quick response.
@blueelvis I'm familiar with the run-anyway option, but am not at liberty to use it.
Same goes for unblocking the binary for manual-installation.
I'm spinning up Kubernetes manually, as I assume other users facing this issue would.

[blueelvis]

@afbjorklund - Yep, this would require the executables to be signed. I have also resorted to using Chocolatey for the installation as it takes care of this.

@Ehud-Banunu - You could try to install minikube using Chocolatey like this - https://minikube.sigs.k8s.io/docs/start/windows/

Just curious, are you using a corporate laptop to work with minikube?

[tstromberg]

#sig-release issue: kubernetes/release#839

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[medyagh]

how about we add alternative way of installing using something like curl.

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[medyagh]

@blueelvis do u have suggestions howe we can become a known publisher?

[tstromberg]

This issue appears to be a duplicate of #4841, do you mind if we move the conversation there?

Ths way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using /reopen. If you have additional information to share, please add it to the new issue.

Thank you for reporting this!