Neil Wilson

You can do it, but it is a bit involved - as `Fatal` calls `os.Exit()` ``` func testOsExit(t *testing.T, funcName string, testFunc func(*testing.T)) { if os.Getenv(funcName) == "1" { testFunc(t)...

That's into philosophical arguments about testing. Subprocess testing has been part of `go test` lore since the start. The code above is adapted from a 2014 presentation by Andrew Gerrand....

I've added a PR. Apologies for not getting onto the tests. They looked like they may need a bit of refactoring and I haven't had the bandwidth to tackle them

First thing to sort out is how to update the modules, so that Go module updates work correctly. The standard main.go has dependencies on 'k8s.io/kubernetes' and 'k8s.io/component-base' Component base isn't...

``` $ go get k8s.io/[email protected] go: finding k8s.io/apiextensions-apiserver v0.0.0 go: finding k8s.io/apiserver v0.0.0 go: finding k8s.io/kube-proxy v0.0.0 go: finding k8s.io/cloud-provider v0.0.0 go: finding k8s.io/kube-scheduler v0.0.0 go: finding k8s.io/cluster-bootstrap v0.0.0 go:...

I've spent a day struggling with 1.15 and I've still not managed to get the dependencies sorted out for the cloud-provider. It looks like I'll have to manually code 'replace'...

In terms of a publishing process, the one I use with Hashicorp to publish our terraform provider is a good one. I go on a slack channel and ask them...

> @NeilW's idea of providing a dummy provider is interesting, though I'm not sure I fully grasped yet how that'd be consumed. Less that we would consume cloud-provider and more...

In terms of updating to 1.15 - Strip your go.mod down to just the requires for your provider - Auto generate the k8s.io require and replace entries using something [like...

[cilium-sysdump-20201231-153706.zip](https://github.com/cilium/cilium/files/5757679/cilium-sysdump-20201231-153706.zip)