docs: Add maintenance pages

modules/concepts/nav.adoc

@@ -26,4 +26,7 @@
 *** xref:observability/logging.adoc[Logging]
 *** xref:observability/containerdebug.adoc[Container environment]
 *** xref:observability/telemetry.adoc[Telemetry]
+** Maintenance
+*** xref:maintenance/crds.adoc[CRD maintenance]
+*** xref:maintenance/eos.adoc[End-of-Support check]
 ** xref:container-images.adoc[]

modules/concepts/pages/maintenance/crds.adoc

@@ -0,0 +1,31 @@
+= CustomResourceDefinition (CRD) maintenance
+:k8s-webhook-config: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#configure-customresourcedefinition-to-use-conversion-webhooks
+
+Since SDP 25.11.0 some operators maintain the CRD on their own without relying on Helm or other deployment tools.
+The primary reason for this is that the operator is able to inject a {k8s-webhook-config}[conversion webhook configuration] with an up-to-date `caBundle`.
+The operator generates a CA (and a leaf certificate) used by the conversion webhook automatically which is additionally rotated every 24 hours.
+This requires the operator to continuously update the `caBundle` field of the webhook configuration.
+
+This maintenance process can be disabled via a Helm value if desired.
+
+[WARNING]
+====
+It should be noted that when CRD maintenance is disabled, the operator will not deploy and manage the CRDs.
+The CRDs need to be deployed manually and the conversion webhook is disabled.
+As a result, only custom resources of the stored version can be used.
+Only use this setting if you know what you are doing!
+====
+
+[NOTE]
+====
+The following section describe the available fields as well as their default and supported values.
+====
+
+[source,yaml]
+----
+maintenance:
+  customResourceDefinitions:
+    maintain: true # <1>
+----
+
+<1> Boolean: `true`, `false`

modules/concepts/pages/maintenance/eos.adoc

@@ -0,0 +1,25 @@
+= End-of-Support (EoS) check
+
+Since SDP 25.11.0 operators emit a warning message on startup and in a regular interval when it may have reached end-of-support.
+Most of our operators reach end-of-support one year after they have been released which roughly translates to three SDP releases.
+This is in accordance with our xref:compliance:policies.adoc[support policy].
+
+The interval can be adjusted or the check can be disabled completely via Helm values.
+
+[NOTE]
+====
+The following sections describe the available fields as well as their default and supported values.
+====
+
+[source,yaml]
+----
+maintenance:
+  endOfSupportCheck:
+    enabled: true # <1>
+    mode: offline # <2>
+    interval: 24h # <3>
+----
+
+<1> Boolean: `true`, `false`
+<2> Enum: `offline` (currently no other options available)
+<3> Duration: Any duration according to xref:reference:duration.adoc[this format]