state validation fails due to new default namespace labels

[mattfenwick]

This happens on newer kube versions, see: kubernetes/kubernetes#96968

Logs:
Untitled.txt

time="2021-04-09T09:52:57Z" level=fatal msg="for namespace y, expected labels map[ns:y] (found map[kubernetes.io/metadata.name:y ns:y])\n
github.com/mattfenwick/cyclonus/pkg/connectivity.(*TestCaseState).verifyClusterStateHelper
  /Users/mfenwick/go/src/github.com/mattfenwick/cyclonus/pkg/connectivity/testcasestate.go:238
github.com/mattfenwick/cyclonus/pkg/connectivity.(*TestCaseState).VerifyClusterState
  /Users/mfenwick/go/src/github.com/mattfenwick/cyclonus/pkg/connectivity/testcasestate.go:286
github.com/mattfenwick/cyclonus/pkg/connectivity.(*Interpreter).ExecuteTestCase
  /Users/mfenwick/go/src/github.com/mattfenwick/cyclonus/pkg/connectivity/interpreter.go:85
github.com/mattfenwick/cyclonus/pkg/cli.RunGenerateCommand\n\t/Users/mfenwick/go/src/github.com/mattfenwick/cyclonus/pkg/cli/generate.go:135\ngithub.com/mattfenwick/cyclonus/pkg/cli.SetupGenerateCommand.func1\n\t/Users/mfenwick/go/src/github.com/mattfenwick/cyclonus/pkg/cli/generate.go:44\ngithub.com/spf13/cobra.
(*Command).execute\n\t/Users/mfenwick/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:846\ngithub.com/spf13/cobra.
(*Command).ExecuteC\n\t/Users/mfenwick/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950\ngithub.com/spf13/cobra.
(*Command).Execute\n\t/Users/mfenwick/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887\ngithub.com/mattfenwick/cyclonus/pkg/cli.RunRootCommand\n\t/Users/mfenwick/go/src/github.com/mattfenwick/cyclonus/pkg/cli/root.go:13\nmain.main\n\t/Users/mfenwick/go/src/github.com/mattfenwick/cyclonus/cmd/cyclonus/main.go:8\nruntime.main\n\t/usr/local/Cellar/go/1.15.5/libexec/src/runtime/proc.go:204\nruntime.goexit\n\t/usr/local/Cellar/go/1.15.5/libexec/src/runtime/asm_amd64.s:1374"

TODOs:

• get a cluster of 1.21 to repro this against
• come up with some code that works on both <= 1.20 and >= 1.21
• (maybe) just ignore extra labels
• (maybe) detect cluster version and do the right thing automatically
• (maybe) provide a CLI switch to turn on/off the labels

[mattfenwick]

see #119

[mattfenwick]

Resolution: read actual labels from kubernetes cluster, using those as the basis for the model.