Configure a self-hosted deployment

Last updated: September 8, 2026

Use this article when you need to change configuration for a self-hosted Cysmiq deployment or understand which settings are managed through the Admin Console.

Where configuration lives

  • Admin Console: self-hosted Cysmiq deployments are configured through the Admin Console.
  • Application access: configure the application domain, exposure mode, ingress, HTTPProxy, NodePort, and TLS settings from the deployment configuration.
  • Infrastructure services: choose embedded or external MySQL and RabbitMQ, then configure storage, resource limits, scaling, networking, proxy, mail, and telemetry settings as needed.

Common reasons to update configuration

  • Traffic and access: update hostnames, ingress class, TLS, proxy, network policy, or egress CIDR settings.
  • Capacity: adjust persistent storage, CPU and memory requests or limits, service replica counts, MySQL settings, RabbitMQ message size or consumer timeout, PHP memory, scan concurrency, repository concurrency share, dependency timeout, or queue timeout. When Configure resource requests and limits is enabled, include the fixed disk-monitoring allocations for embedded data services in capacity planning.
  • Managed infrastructure: switch to an external database or RabbitMQ, use a custom service account, or add application environment variables required by your environment.

What to check first

  • Confirm whether the deployment uses embedded or external services before changing database or RabbitMQ settings.
  • Check the current Admin Console configuration before applying upgrades or changing resource limits.
  • Coordinate hostname, TLS, proxy, firewall, and service-account changes with the team that manages the Kubernetes cluster.

Stable 1.14.4 defaults to MySQL 8.4.11 for the embedded database.

Canonical docs

For the maintained list of configuration options, defaults, and field descriptions, see Self-hosting configuration.

Contact support if

  • You are unsure which setting controls a deployment, networking, storage, database, RabbitMQ, or scanning behavior.
  • A configuration change does not apply after saving or upgrading.
  • The Admin Console reports validation, preflight, or deployment errors after a configuration update.