[FLINK-31717] Unit tests running with local kube config

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: kubernetes-operator-1.4.0
• Fix Version/s: kubernetes-operator-1.6.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Mate Czagany
• Reporter: Matyas Orhidi
• Created: 03/Apr/23 20:28
• Updated: 12/May/23 11:52
• Resolved: 12/May/23 11:52

Description

Some unit tests are using local kube environment. This can be dangerous when pointing to sensitive clusters e.g. in prod.

2023-04-03 12:32:53,956 i.f.k.c.Config [DEBUG] Found for Kubernetes config at: [/Users/<redacted>/.kube/config].

A misconfigured kube config environment revealed the issue:

[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.012 s <<< FAILURE! - in org.apache.flink.kubernetes.operator.FlinkOperatorTest
[ERROR] org.apache.flink.kubernetes.operator.FlinkOperatorTest.testConfigurationPassedToJOSDK Time elapsed: 0.008 s <<< ERROR!
java.lang.NullPointerException
at org.apache.flink.kubernetes.operator.FlinkOperatorTest.testConfigurationPassedToJOSDK(FlinkOperatorTest.java:63)

[ERROR] org.apache.flink.kubernetes.operator.FlinkOperatorTest.testLeaderElectionConfig Time elapsed: 0.004 s <<< ERROR!
java.lang.NullPointerException
at org.apache.flink.kubernetes.operator.FlinkOperatorTest.testLeaderElectionConfig(FlinkOperatorTest.java:108)

Issue Links

• links to: GitHub Pull Request #587