Revert "fix: make application templates namespaced (#694)" (#719)

* Revert "fix: make application templates namespaced (#694)"

This reverts commit b326be3.

* revert changelog

* update nix crate hashes

Author: razvan

CHANGELOG.md

@@ -31,7 +31,6 @@ All notable changes to this project will be documented in this file.
 - Internal operator refactoring: introduce dereference() and validate() steps in the reconciler for spark application, spark connect and spark history server([#687]).
 - test: Bump vector-aggregator to 0.55.0, replace /graphql call with gRPC call ([#689]).
 - Fix the `SparkApplication` CRD description, which incorrectly described it as a "Spark cluster stacklet" rather than a Spark application ([#705]).
-- BREAKING: make application templates namespaced instead of cluster wide objects ([#694]).
 
 [#674]: https://github.com/stackabletech/spark-k8s-operator/pull/674
 [#679]: https://github.com/stackabletech/spark-k8s-operator/pull/679
@@ -40,7 +39,6 @@ All notable changes to this project will be documented in this file.
 [#687]: https://github.com/stackabletech/spark-k8s-operator/pull/687
 [#689]: https://github.com/stackabletech/spark-k8s-operator/pull/689
 [#692]: https://github.com/stackabletech/spark-k8s-operator/pull/692
-[#694]: https://github.com/stackabletech/spark-k8s-operator/pull/694
 [#696]: https://github.com/stackabletech/spark-k8s-operator/pull/696
 [#705]: https://github.com/stackabletech/spark-k8s-operator/pull/705
 [#708]: https://github.com/stackabletech/spark-k8s-operator/pull/708

Cargo.nix

@@ -5,23 +5,13 @@ Spark application templates are used to define reusable configurations for Spark
 When you have many applications with similar configurations, templates can help you avoid duplication by grouping common settings together.
 Application templates are available for the `v1alpha1` version of the SparkApplication custom resource and share the exact same structure as the SparkApplication resource, but with some differences in the way the operator handles them:
 
-1. Application templates are namespace-scoped resources, just like Spark applications.
-  This means that a SparkApplication can only reference templates from its own namespace.
+1. Application templates are cluster wide resources, while Spark application resources are namespace-scoped.
+  This means that application templates can be used across multiple namespaces, while Spark application resources are limited to the namespace they are created in.
 2. Application templates are not reconciled by the operator, but must be referenced from a SparkApplication resource to be applied. This means that changes to an application template will not automatically trigger updates to SparkApplication resources that reference it.
 3. An application can reference multiple application templates, and the settings from these templates will be merged together. The merging order of the templates is indicated by their index in the reference list. The application fields have the highest precedence and will override any conflicting settings from the templates. This allows you to have a base template with common settings and then override specific settings in the application resource as needed.
 4. Application template references are immutable in the sense that once applied to an application they cannot be changed again. Currently templates are applied upon the creation of the application, and any changes to the template references after that will be ignored.
 5. Application and template CRDs must have the exact same versions. Currently only `v1alpha1` is supported.
 
-== Migrating from cluster-scoped templates
-
-IMPORTANT: Application templates used to be cluster wide resources when they were first released. This was a mistake. Many users do not have the access rights to create cluster scoped resources and so the templates are now namespace scoped.
-
-If you are migrating from older installations where templates were treated as cluster-wide resources, account for the following:
-
-1. Recreate each template in every namespace where SparkApplications use it.
-2. Keep template names consistent per namespace if you want the same application annotations to continue working.
-3. Cross-namespace template references are no longer resolved; templates and applications must be in the same namespace.
-4. Update GitOps/automation manifests to create templates as namespace-targeted resources before reconciling dependent SparkApplications.
 == Examples
 
 Applications use `metadata.annotations` to reference application templates as shown below:

crate-hashes.json

@@ -4657,7 +4657,7 @@ spec:
     shortNames:
     - sparkapptemplate
     singular: sparkapplicationtemplate
-  scope: Namespaced
+  scope: Cluster
   versions:
   - additionalPrinterColumns: []
     name: v1alpha1

docs/modules/spark-k8s/pages/usage-guide/app_templates.adoc

@@ -322,47 +322,6 @@ mod tests {
         assert_eq!(merged.spec.args, vec!["arg1", "arg2"]);
     }
 
-    #[test]
-    fn test_deep_merge_metadata_namespace_overlay_wins() {
-        let base = serde_yaml::from_str::<crate::crd::v1alpha1::SparkApplication>(indoc! {r#"
-            ---
-            apiVersion: spark.stackable.tech/v1alpha1
-            kind: SparkApplication
-            metadata:
-              name: base-app
-              namespace: template-namespace
-            spec:
-              mode: cluster
-              mainApplicationFile: base.py
-              sparkImage:
-                productVersion: "3.5.0"
-        "#})
-        .unwrap();
-
-        let overlay = serde_yaml::from_str::<crate::crd::v1alpha1::SparkApplication>(indoc! {r#"
-            ---
-            apiVersion: spark.stackable.tech/v1alpha1
-            kind: SparkApplication
-            metadata:
-              name: overlay-app
-              namespace: app-namespace
-            spec:
-              mode: cluster
-              mainApplicationFile: overlay.py
-              sparkImage:
-                productVersion: "3.5.1"
-        "#})
-        .unwrap();
-
-        let merged = deep_merge(&base, &overlay);
-
-        assert_eq!(
-            merged.metadata.namespace,
-            Some("app-namespace".to_string()),
-            "overlay namespace should take precedence"
-        );
-    }
-
     #[test]
     fn test_deep_merge_spark_conf() {
         let base = serde_yaml::from_str::<crate::crd::v1alpha1::SparkApplication>(indoc! {r#"

extra/crds.yaml

@@ -44,9 +44,6 @@ pub enum Error {
         template_name: String,
         source: stackable_operator::kube::Error,
     },
-
-    #[snafu(display("object has no namespace"))]
-    ObjectHasNoNamespace,
 }
 
 #[versioned(
@@ -69,7 +66,6 @@ pub mod versioned {
         group = "spark.stackable.tech",
         plural = "sparkapptemplates",
         shortname = "sparkapptemplate",
-        namespaced
     ))]
     #[derive(Clone, CustomResource, Debug, Deserialize, JsonSchema, Serialize)]
     #[serde(rename_all = "camelCase")]
@@ -267,10 +263,8 @@ pub(crate) async fn merge_application_templates(
         // In the future if we support additional strategies in addition to "enforce",
         // this list might not be identical to the one in `merge_template_options`
         // because some objects might be missing.
-        let namespace = spark_application_namespace(spark_application)?;
         let templates = resolve(
             client,
-            namespace,
             &merge_template_options.template_names,
             merge_template_options.apply_strategy,
         )
@@ -323,28 +317,16 @@ pub(crate) async fn merge_application_templates(
     Ok(default_result)
 }
 
-fn spark_application_namespace(
-    spark_application: &super::v1alpha1::SparkApplication,
-) -> Result<&str, Error> {
-    spark_application
-        .metadata
-        .namespace
-        .as_deref()
-        .ok_or(Error::ObjectHasNoNamespace)
-}
-
 async fn resolve(
     client: &stackable_operator::client::Client,
-    namespace: &str,
     template_names: &[String],
     apply_strategy: TemplateApplyStrategy,
 ) -> Result<Vec<v1alpha1::SparkApplicationTemplate>, Error> {
     if template_names.is_empty() {
         return Ok(vec![]);
     }
 
-    let templates_api =
-        Api::<v1alpha1::SparkApplicationTemplate>::namespaced(client.as_kube_client(), namespace);
+    let templates_api = Api::<v1alpha1::SparkApplicationTemplate>::all(client.as_kube_client());
     let mut resolved_templates = Vec::new();
     for template_name in template_names {
         let template_res = templates_api
@@ -452,53 +434,6 @@ mod tests {
         assert!(options.template_names.is_empty());
     }
 
-    #[test]
-    fn spark_application_namespace_returns_namespace() {
-        let spark_application =
-            serde_yaml::from_str::<crate::crd::v1alpha1::SparkApplication>(indoc! {r#"
-                ---
-                apiVersion: spark.stackable.tech/v1alpha1
-                kind: SparkApplication
-                metadata:
-                  name: app-with-templates
-                  namespace: default
-                spec:
-                  mode: cluster
-                  mainApplicationFile: local:///app.py
-                  sparkImage:
-                    productVersion: "3.5.8"
-            "#})
-            .unwrap();
-
-        assert_eq!(
-            spark_application_namespace(&spark_application).unwrap(),
-            "default"
-        );
-    }
-
-    #[test]
-    fn spark_application_namespace_returns_error_when_missing() {
-        let spark_application =
-            serde_yaml::from_str::<crate::crd::v1alpha1::SparkApplication>(indoc! {r#"
-                ---
-                apiVersion: spark.stackable.tech/v1alpha1
-                kind: SparkApplication
-                metadata:
-                  name: app-with-templates
-                spec:
-                  mode: cluster
-                  mainApplicationFile: local:///app.py
-                  sparkImage:
-                    productVersion: "3.5.8"
-            "#})
-            .unwrap();
-
-        assert!(matches!(
-            spark_application_namespace(&spark_application),
-            Err(Error::ObjectHasNoNamespace)
-        ));
-    }
-
     impl RoundtripTestData for v1alpha1::SparkApplicationTemplateSpec {
         fn roundtrip_test_data() -> Vec<Self> {
             // SparkApplicationTemplateSpec is just a wrapper around SparkApplicationSpec