docs

Signed-off-by: Attila Mészáros <[email protected]>

Author: csviri

Diff for: sample-operators/controller-namespace-deletion/README.md

@@ -0,0 +1,8 @@
+This sample demonstrates the workaround for problem when a namespace
+is being deleted with a running controller, that watches resources
+in its own namespace. If the pod or other underlying resources (role,
+role binding, service account) are deleted before the cleanup of
+the custom resource the namespace deletion is stuck.
+
+see also: https://github.com/operator-framework/java-operator-sdk/pull/2528
+

Diff for: sample-operators/controller-namespace-deletion/src/test/java/io/javaoperatorsdk/operator/sample/ControllerNamespaceDeletionE2E.java

@@ -10,6 +10,7 @@
 
 import org.junit.jupiter.api.BeforeEach;
 import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.condition.EnabledIfSystemProperty;
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
 
@@ -39,7 +40,7 @@ class ControllerNamespaceDeletionE2E {
   KubernetesClient client;
 
   // not for local mode by design
-  // @EnabledIfSystemProperty(named = "test.deployment", matches = "remote")
+  @EnabledIfSystemProperty(named = "test.deployment", matches = "remote")
   @Test
   void customResourceCleanedUpOnNamespaceDeletion() {
     deployController();
@@ -60,7 +61,7 @@ void customResourceCleanedUpOnNamespaceDeletion() {
       assertThat(ns).isNull();
     });
 
-    log.info("Removing finalizers from role and role bing");
+    log.info("Removing finalizers from role and role bing and service account");
     removeRoleAndRoleBindingFinalizers();
 
     await().timeout(Duration.ofSeconds(20)).untilAsserted(() -> {