# Release Notes — 2.101 Covers the `2.101.x` Helm chart series. Most recent patch: **2.101.0**. _Unless a subsection says otherwise, changes apply to both Monad SaaS and self-hosted._ ## New features & improvements **Self-hosted only** - **More control over self-managed installs** — the chart now fits your cluster's own scheduling, registry, secret, and GitOps conventions. Cluster-wide `global.nodeSelector`, `tolerations`, `affinity`, and `imagePullSecrets` reach every pod, including NATS and the pipeline pods the operator creates; `global.image.registry` moves the Monad, pipeline, NATS, VictoriaMetrics, and per-pipeline Dragonfly images to your registry; the release can have any name, which suits Argo CD; and you can supply your own database Secret, CloudNativePG StorageClass, and Kratos Secret. CRDs now stay in place on uninstall. The chart ships three tested example values files. [Docs →](https://app.monad.com/docs/guides/self-managed/install) (2.101.0) - *Access:* opt-in — set the new keys in your values file; the install guide and the chart's `examples/` show each one. - *Deprecated:* `operator.env.MONAD_ENV_*` still works; use `operator.pipelineEnv` instead. ## Breaking changes **Self-hosted only** - **If you set `global.image.registry`, mirror the pipeline, VictoriaMetrics, and Dragonfly images before upgrading** — these images now follow `global.image.registry` as NATS already did, and pipeline images also follow the operator's `image.repository`. Either change restarts every pipeline pod once. To keep pipeline images where they are, set `operator.env.MONAD_PIPELINE_IMAGE_REGISTRY`. (2.101.0) - **Some values now fail the upgrade instead of being ignored** — turning NATS or Dragonfly off without giving its URL, or enabling backups without `destinationPath`, now fails `helm upgrade`, and `nats.global.image.registry` is ignored (use `global.image.registry`). Enabled backups now run daily unless you set a schedule. A pod setting the operator can't read now stops the operator's rollout, and the previous operator keeps running. (2.101.0) - **Jobs and CronJobs no longer inherit their component's probes** — a Job or CronJob that needs a probe must set its own `probes`. A field you set under `postgresql.cnpg.spec` now replaces the generated one instead of merging with it. (2.101.0) ## Need help? See the [Monad docs](https://app.monad.com/docs) for setup guides and reference, or reach out to Monad Customer Support at [support@monad.com](mailto:support@monad.com) or via your dedicated Slack customer channel. :::note Self-hosted deployments upgrade to a `2.101.x` release with `helm upgrade`. Review the **Breaking changes** section above before upgrading; when it says "None," the upgrade is drop-in. :::