docs: document addSafeToEvictAnnotation and 1.49 default change (DEV-1467)

Add an `addSafeToEvictAnnotation` reference entry to the Helm configuration
page describing the `enabled`/`value` fields, the YAML snippet, and the impact
of each combination on the Kubernetes cluster autoscaler. Add a 1.49.0 release
note covering the default flip from `value: true` to `value: false` and how to
restore the previous behavior.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Javier Lopez <javier@okteto.com>

Author: jLopezbarb

src/content/release-notes.mdx

@@ -7,6 +7,18 @@ id: release-notes
 
 import Image from '@theme/Image';
 
+## 1.49.0
+
+<!-- TODO(release): confirm the release date and the compatible Okteto CLI version (3.24.x is a placeholder) before cutting 1.49 -->
+October 2026
+
+This version is compatible with Kubernetes versions 1.33 to 1.35 \
+Okteto Chart release 1.49 is designed to work with [Okteto CLI 3.24.x](https://github.com/okteto/okteto/releases)
+
+### Important Notes {#important-notes-1.49}
+
+- **`safe-to-evict` annotation now defaults to `false`**: Okteto marks the pods it creates in development Namespaces as not safe to evict, so the Kubernetes cluster autoscaler no longer scales down nodes that run active development sessions. Previously these pods were marked safe to evict, which could restart development services during scale-down. To restore the previous behavior, set [`addSafeToEvictAnnotation.value`](self-hosted/helm-configuration.mdx#addsafetoevictannotation) to `true` <!-- DEV-1467, app#10402 -->
+
 ## 1.48.0
 
 4 September 2026

src/content/self-hosted/helm-configuration.mdx

@@ -796,6 +796,29 @@ The webhook service. Ingress creation, generation of hostnames, enforcement of p
 
 ## Advanced Configuration
 
+### addSafeToEvictAnnotation
+
+Controls the [`cluster-autoscaler.kubernetes.io/safe-to-evict`](https://kubernetes.io/docs/reference/labels-annotations-taints/#cluster-autoscaler-kubernetes-io-safe-to-evict) annotation that Okteto adds to the pods it creates in development Namespaces.
+
+- `enabled`: Whether Okteto adds the annotation. Enabled by default. If a pod already carries the annotation, Okteto keeps the existing value.
+- `value`: The value Okteto sets for the annotation, `true` or `false`. Defaults to `false`.
+
+```yaml
+addSafeToEvictAnnotation:
+  enabled: true
+  value: false
+```
+
+The annotation controls whether the Kubernetes cluster autoscaler may evict a pod when it scales down the node running it:
+
+- `enabled: true`, `value: false` (default): marks Okteto pods as not safe to evict. The autoscaler will not scale down a node that runs one of these pods, regardless of the pod's shape. This keeps active development sessions stable, at the cost of slower node scale-down and potentially higher infrastructure cost.
+- `enabled: true`, `value: true`: marks Okteto pods as safe to evict, even when the autoscaler would otherwise protect them (for example, pods with local storage). This favors aggressive scale-down and cost savings, at the cost of development sessions restarting during scale-down.
+- `enabled: false`: Okteto does not add the annotation, and the autoscaler falls back to its own default heuristics. This does not reliably prevent eviction — for many pod shapes it behaves like `value: true` — so it is not equivalent to `value: false`. Use it when you want the cluster to decide.
+
+:::note
+Before Okteto Chart 1.49, this annotation defaulted to `value: true`. To keep that behavior after upgrading, set `addSafeToEvictAnnotation.value` to `true`.
+:::
+
 ### affinity
 
 Apply default affinities to pods deployed in namespaces created by Okteto.