Cozystack Cluster Configuration on Cozystack

Cozystack ConfigMap Reference

Mon, 01 Jan 0001 00:00:00 +0000

This page explains the role of Cozystack’s main ConfigMap and provides a full reference for its values.

Cozystack’s main configuration is defined by a single Kubernetes ConfigMap. This ConfigMap includes Cozystack bundle and components setup, key network settings, exposed services, and other options.

Example

Here’s an example of configuration for installing Cozystack with bundle paas-full, with root host “example.org”, and Cozystack Dashboard and API exposed and available to users:

apiVersion: v1
kind: ConfigMap
metadata:
 name: cozystack
 namespace: cozy-system
data:
 bundle-name: "paas-full"
 root-host: "example.org"
 api-server-endpoint: "https://api.example.org:443"
 expose-services: "dashboard,api"
 ipv4-pod-cidr: "10.244.0.0/16"
 ipv4-pod-gateway: "10.244.0.1"
 ipv4-svc-cidr: "10.96.0.0/16"
 ipv4-join-cidr: "100.64.0.0/16"

Reference

Value (`data.*`)	Bundles	Description
`bundle-name`	all	Name of bundle to use for installation.
`bundle-enable`	all	Optional bundle components included in the installation. Read more about this option in “How to enable and disable bundle components”.
`bundle-disable`	all	Bundle components excluded (disabled) from the installation. Read more about this option in “How to enable and disable bundle components”.
`values-<component>`	all	JSON or YAML formatted values passed to specific component installation. Read more about this option in “how to overwrite parameters for specific components”.
`root-host`	all	The main domain for all services created under Cozystack, such as the dashboard, Grafana, Keycloak, etc.
`api-server-endpoint`	all	Used for generating kubeconfig files for your users. It is recommended to use a routable FQDN or IP address instead of local-only addresses.
`telemetry-enabled`	all	Enable telemetry feature in Cozystack (default: `true`).
`expose-services`	all	Comma-separated list of services to expose to the internet. Possible values: `api,dashboard,cdi-uploadproxy,vm-exportproxy`.
`expose-ingress`	all	Ingress controller to use for exposing services. (default: `tenant-root`)
`expose-external-ips`	all	Comma-separated list of external IPs used for the specified ingress controller. If not specified, a LoadBalancer service is used by default.
`ipv4-pod-cidr`	`paas-full`, `distro-full`	The pod subnet used by Pods to assign IPs
`ipv4-pod-gateway`	`paas-full`	The gateway address for the pod subnet
`ipv4-svc-cidr`	`paas-full`, `distro-full`	The pod subnet used by Services to assign IPs
`ipv4-join-cidr`	`paas-full`	The `join` subnet, as a special subnet for network communication between the Node and Pod. Follow the kube-ovn documentation to learn more about these options.
`oidc-enabled`	`paas-full`, `paas-hosted`	Enable oidc feature in Cozystack (default: `false`)
`cpu-allocation-ratio`	`paas-full`, `paas-hosted`	CPU allocation ratio: `1/cpu-allocation-ratio` CPU requested per 1 vCPU. Defaults to 10. See Resource Management for detailed explanation and examples.

Cozystack Bundles: Overview and Comparison

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Bundles are pre-defined combinations of Cozystack components. Each bundle is tested, versioned, and guaranteed to work as a unit. They simplify installation, reduce the risk of misconfiguration, and make it easier to choose the right set of features for your deployment.

This guide is for infrastructure engineers, DevOps teams, and platform architects planning to deploy Cozystack in different environments. It explains how Cozystack bundles help tailor the installation to specific needs—whether you’re building a fully featured platform-as-a-service or just need a minimal Kubernetes cluster.

Cozystack Components Reference

Mon, 01 Jan 0001 00:00:00 +0000

Overwriting Component Parameters

You might want to override specific options for the components. To achieve this, you must specify values in JSON or YAML format using the data.values-<component> option in the Cozystack ConfigMap.

For example, if you want to overwrite k8sServiceHost and k8sServicePort for cilium, take a look at its values.yaml file.

Then specify these options in the values-cilium section of your Cozystack configuration, as shown below:

apiVersion: v1
kind: ConfigMap
metadata:
 name: cozystack
 namespace: cozy-system
data:
 bundle-name: "distro-full"
 ipv4-pod-cidr: "10.244.0.0/16"
 ipv4-svc-cidr: "10.96.0.0/16"
 values-cilium: |
 cilium:
 k8sServiceHost: 11.22.33.44
 k8sServicePort: 6443

Enabling and Disabling Components

Bundles have optional components that need to be explicitly enabled (included) in the installation. Regular bundle components can, on the other hand, be disabled (excluded) from the installation, when you don’t need them.

Licenses

Mon, 01 Jan 0001 00:00:00 +0000

This page lists the licenses for the primary components packaged with Cozystack. Cozystack-maintained charts, CRDs, controllers, and application APIs are licensed under Apache-2.0. When a package vendors or deploys an upstream component, the table shows the upstream component license.

This reference covers top-level Cozystack packages from packages/core, packages/system, packages/apps, and packages/extra, plus the primary managed workload runtimes. Container images can include additional operating-system packages and library dependencies with their own licenses.

Core Packages

Package	Component	License	Source
`core/flux-aio`	Cozystack Flux AIO manifests	Apache-2.0	source
`core/installer`	Cozystack installer chart	Apache-2.0	source
`core/platform`	Cozystack Platform Package chart	Apache-2.0	source
`core/talos`	Cozystack Talos assets	Apache-2.0	source
`core/testing`	Cozystack test chart	Apache-2.0	source

System Packages

Package	Component	License	Source
`system/application-definition-crd`	Cozystack ApplicationDefinition CRD	Apache-2.0	source
`system/backup-controller`	Cozystack backup controller	Apache-2.0	source
`system/backupstrategy-controller`	Cozystack backup strategy controller	Apache-2.0	source
`system/bootbox`	Tinkerbell Smee	Apache-2.0	source
`system/bootbox-rd`	Cozystack Bootbox resource definition	Apache-2.0	source
`system/bucket`	S3 Manager	Apache-2.0	source
`system/bucket-rd`	Cozystack Bucket resource definition	Apache-2.0	source
`system/capi-operator`	Cluster API Operator	Apache-2.0	source
`system/capi-providers-bootstrap`	Cluster API kubeadm bootstrap provider	Apache-2.0	source
`system/capi-providers-core`	Cluster API core provider	Apache-2.0	source
`system/capi-providers-cpprovider`	Kamaji Cluster API control-plane provider	Apache-2.0	source
`system/capi-providers-infraprovider`	KubeVirt Cluster API infrastructure provider	Apache-2.0	source
`system/cert-manager`	cert-manager	Apache-2.0	source
`system/cert-manager-crds`	cert-manager CRDs	Apache-2.0	source
`system/cert-manager-issuers`	Cozystack cert-manager issuers	Apache-2.0	source
`system/cilium`	Cilium	Apache-2.0	source
`system/cilium-networkpolicy`	Cozystack Cilium network policies	Apache-2.0	source
`system/clickhouse-operator`	Altinity ClickHouse Operator	Apache-2.0	source
`system/clickhouse-rd`	Cozystack ClickHouse resource definition	Apache-2.0	source
`system/cluster-autoscaler`	Kubernetes Cluster Autoscaler	Apache-2.0	source
`system/clustersecret-operator`	SAP ClusterSecret Operator	Apache-2.0	source
`system/coredns`	CoreDNS	Apache-2.0	source
`system/cozy-proxy`	cozy-proxy	Apache-2.0	source
`system/cozystack-api`	Cozystack API	Apache-2.0	source
`system/cozystack-basics`	Cozystack basics	Apache-2.0	source
`system/cozystack-controller`	Cozystack controller	Apache-2.0	source
`system/cozystack-scheduler`	Cozystack scheduler	Apache-2.0	source
`system/dashboard`	Cozystack dashboard	Apache-2.0	source
`system/etcd-operator`	Aenix etcd Operator	Apache-2.0	source
`system/etcd-rd`	Cozystack etcd resource definition	Apache-2.0	source
`system/external-dns`	ExternalDNS	Apache-2.0	source
`system/external-dns-rd`	Cozystack ExternalDNS resource definition	Apache-2.0	source
`system/external-secrets-operator`	External Secrets Operator	Apache-2.0	source
`system/flux-plunger`	Cozystack Flux plunger	Apache-2.0	source
`system/fluxcd`	ControlPlane Flux instance chart; Flux controllers	AGPL-3.0; Apache-2.0	charts, flux
`system/fluxcd-operator`	ControlPlane Flux Operator	AGPL-3.0	source
`system/foundationdb-operator`	FoundationDB Kubernetes Operator	Apache-2.0	source
`system/foundationdb-rd`	Cozystack FoundationDB resource definition	Apache-2.0	source
`system/gateway-api-crds`	Kubernetes Gateway API CRDs	Apache-2.0	source
`system/goldpinger`	Goldpinger	Apache-2.0	source
`system/gpu-operator`	NVIDIA GPU Operator	Apache-2.0	source
`system/grafana-operator`	Grafana Operator	Apache-2.0	source
`system/hami`	HAMi	Apache-2.0	source
`system/harbor`	Harbor Helm chart	Apache-2.0	source
`system/harbor-rd`	Cozystack Harbor resource definition	Apache-2.0	source
`system/hetzner-robotlb`	RobotLB	MIT	source
`system/http-cache-rd`	Cozystack HTTP cache resource definition	Apache-2.0	source
`system/info-rd`	Cozystack Info resource definition	Apache-2.0	source
`system/ingress-nginx`	ingress-nginx	Apache-2.0	source
`system/ingress-rd`	Cozystack Ingress resource definition	Apache-2.0	source
`system/kafka-operator`	Strimzi Kafka Operator	Apache-2.0	source
`system/kafka-rd`	Cozystack Kafka resource definition	Apache-2.0	source
`system/kamaji`	Kamaji	Apache-2.0	source
`system/keycloak`	Keycloak	Apache-2.0	source
`system/keycloak-configure`	Cozystack Keycloak configuration job	Apache-2.0	source
`system/keycloak-operator`	KubeRocketCI Keycloak Operator	Apache-2.0	source
`system/kilo`	Kilo	Apache-2.0	source
`system/kubeovn`	Kube-OVN chart	Apache-2.0	source
`system/kubeovn-plunger`	Cozystack Kube-OVN plunger	Apache-2.0	source
`system/kubeovn-webhook`	Cozystack Kube-OVN webhook	Apache-2.0	source
`system/kubernetes-rd`	Cozystack Kubernetes resource definition	Apache-2.0	source
`system/kubevirt`	KubeVirt	Apache-2.0	source
`system/kubevirt-cdi`	KubeVirt Containerized Data Importer	Apache-2.0	source
`system/kubevirt-cdi-operator`	KubeVirt CDI Operator	Apache-2.0	source
`system/kubevirt-csi-node`	KubeVirt CSI driver	Apache-2.0	source
`system/kubevirt-instancetypes`	KubeVirt common instancetypes	Apache-2.0	source
`system/kubevirt-operator`	KubeVirt Operator	Apache-2.0	source
`system/lineage-controller-webhook`	Cozystack lineage controller webhook	Apache-2.0	source
`system/linstor`	LINSTOR Server; LINSTOR CSI	GPL-3.0; Apache-2.0	server, csi
`system/linstor-gui`	LINSTOR GUI	GPL-3.0	source
`system/linstor-scheduler`	LINSTOR scheduler extender	Apache-2.0	source
`system/local-ccm`	Local Cloud Controller Manager	Apache-2.0	source
`system/mariadb-operator`	mariadb-operator	MIT	source
`system/mariadb-rd`	Cozystack MariaDB resource definition	Apache-2.0	source
`system/metallb`	MetalLB	Apache-2.0	source
`system/metrics-server`	Metrics Server	Apache-2.0	source
`system/mongodb-operator`	Percona Operator for MongoDB Helm chart	Apache-2.0	source
`system/mongodb-rd`	Cozystack MongoDB resource definition	Apache-2.0	source
`system/monitoring`	Cozystack monitoring package	Apache-2.0	source
`system/monitoring-agents`	Fluent Bit; kube-state-metrics; node-exporter	Apache-2.0	source
`system/monitoring-rd`	Cozystack Monitoring resource definition	Apache-2.0	source
`system/multus`	Multus CNI	Apache-2.0	source
`system/nats`	NATS Helm chart	Apache-2.0	source
`system/nats-rd`	Cozystack NATS resource definition	Apache-2.0	source
`system/nfs-driver`	CSI Driver NFS	Apache-2.0	source
`system/objectstorage-controller`	Container Object Storage Interface controller	Apache-2.0	source
`system/openbao`	OpenBao Helm chart	MPL-2.0	source
`system/openbao-rd`	Cozystack OpenBao resource definition	Apache-2.0	source
`system/opencost`	OpenCost Helm chart	Apache-2.0	source
`system/opensearch-operator`	OpenSearch Operator	Apache-2.0	source
`system/opensearch-rd`	Cozystack OpenSearch resource definition	Apache-2.0	source
`system/piraeus-operator`	Piraeus Operator	Apache-2.0	source
`system/piraeus-operator-crds`	Piraeus Operator CRDs	Apache-2.0	source
`system/postgres-operator`	CloudNativePG operator chart	Apache-2.0	source
`system/postgres-rd`	Cozystack PostgreSQL resource definition	Apache-2.0	source
`system/prometheus-operator-crds`	Prometheus Operator CRDs chart	Apache-2.0	source
`system/qdrant`	Qdrant Helm chart	Apache-2.0	source
`system/qdrant-rd`	Cozystack Qdrant resource definition	Apache-2.0	source
`system/rabbitmq-operator`	RabbitMQ cluster and topology operators	MPL-2.0	source
`system/rabbitmq-rd`	Cozystack RabbitMQ resource definition	Apache-2.0	source
`system/redis-operator`	Spotahome Redis Operator	Apache-2.0	source
`system/redis-rd`	Cozystack Redis resource definition	Apache-2.0	source
`system/reloader`	Stakater Reloader	Apache-2.0	source
`system/seaweedfs`	SeaweedFS Helm chart	Apache-2.0	source
`system/seaweedfs-rd`	Cozystack SeaweedFS resource definition	Apache-2.0	source
`system/snapshot-controller`	CSI external snapshotter	Apache-2.0	source
`system/tcp-balancer-rd`	Cozystack TCP balancer resource definition	Apache-2.0	source
`system/telepresence`	Telepresence Traffic Manager chart	Apache-2.0	source
`system/tenant-rd`	Cozystack Tenant resource definition	Apache-2.0	source
`system/velero`	Velero Helm chart	Apache-2.0	source
`system/vertical-pod-autoscaler`	Vertical Pod Autoscaler chart	MIT; Apache-2.0	source
`system/vertical-pod-autoscaler-crds`	Vertical Pod Autoscaler CRDs	Apache-2.0	source
`system/victoria-metrics-operator`	VictoriaMetrics Operator chart	Apache-2.0	source
`system/virtualprivatecloud-rd`	Cozystack VPC resource definition	Apache-2.0	source
`system/vm-default-images`	Cozystack VM default image catalog	Apache-2.0	source
`system/vm-disk-rd`	Cozystack VM disk resource definition	Apache-2.0	source
`system/vm-instance-rd`	Cozystack VM instance resource definition	Apache-2.0	source
`system/vpn-rd`	Cozystack VPN resource definition	Apache-2.0	source
`system/vsnap-crd`	CSI VolumeSnapshot CRDs	Apache-2.0	source

Application and Extra Packages

The following packages define Cozystack application APIs and tenant-level extras. Their package source is Apache-2.0; runtime software licenses for managed services are listed in the next section.

Telemetry

Mon, 01 Jan 0001 00:00:00 +0000

This document outlines the telemetry feature within the Cozystack project, detailing the rationale behind data collection, the nature of the data collected, data handling practices, and instructions for opting out.

Why We Collect Telemetry

Cozystack, as an open source project, thrives on community feedback and usage insights. Telemetry data allows maintainers to understand how Cozystack is being used in real-world scenarios. This data informs decisions related to feature prioritization, testing strategies, bug fixes, and overall project evolution. Without telemetry, decisions would rely on guesswork or limited feedback, which might slow down improvement cycles or introduce features that don’t align with users’ needs. Telemetry ensures that development is guided by actual usage patterns and community requirements, fostering a more robust and user-centric platform.