Add an upgrade test case where a single fdb-kubernetes-monitor is not able to connect to the Kubernetes API

[johscheuer]

Description

As expected the upgrade will be stuck until the fdb-kubernetes-monitor can communicate to the K8s API again.

Type of change

Please select one of the options below.

• Other

Discussion

Testing

Ran the test manually:

• [377.644 seconds]
------------------------------
[AfterSuite]
/Users/jscheuermann/go/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_upgrades/operator_upgrades_test.go:55
[AfterSuite] PASSED [0.000 seconds]
------------------------------
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.004 seconds]
------------------------------

Ran 1 of 11 Specs in 377.644 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 10 Skipped
PASS | FOCUSED
FAIL    github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_upgrades      378.067s
FAIL

Documentation

Follow-up

[nicmorales9]

changes look good! just 1 question for my understanding

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: ab2e41f
• Duration 2:39:40
• Result: ❌ FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: cbca28a
• Duration 2:53:53
• Result: ❌ FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[johscheuer]

I looked at the test failures and those are unrelated. Will be looking at them more closely.