Skip to Content
AppendicesPaths and Names

Paths and Names

A lookup table. Most rows link to the page that explains them.

Configuration you write

PathContents
/etc/stratum/config.yamlthe declarative ClusterConfig; see Configuration
/etc/stratum/stratum.envoptional environment for the unit, such as S3 credentials; you create it, root-owned, mode 0600; see Environment for the unit
/etc/stratum/registries.yamlregistry mirrors, in the RKE2/k3s format; you create it, root-owned, mode 0600; see Registry mirrors
/etc/stratum/snapshot.confsnapshot retention and S3 target, written by stratum snapshot schedule; created with mode 0600 and may hold S3 credentials, so keep an existing file root-owned and 0600; see Where retention and the upload target come from
/var/lib/stratum/manifests/manifests the operator applies; see Deploying manifests

Node state

PathContents
/var/lib/stratum/all state: PKI, kubeconfigs, binaries, images, node state
/var/lib/stratum/bin/the payload's binaries, including the ones stratum kubectl and stratum etcdctl run
/var/lib/stratum/images/the payload's image archives
/var/lib/stratum/pki/certificates and keys, and encryption-config.yaml under the CIS profile
/var/lib/stratum/config/node.yamlthe persisted NodeState
/var/lib/stratum/config/manifests/*.yamlthe rendered control-plane static pod manifests; see Hardening
/var/lib/stratum/kubeconfig/admin.confthe admin kubeconfig, on control planes; revocable, see admin.conf and super-admin.conf
/var/lib/stratum/kubeconfig/super-admin.confthe system:masters kubeconfig Stratum itself uses, on control planes
/var/lib/stratum/upgrade/in-progress.jsonpresent from an upgrade's first change until its health gate passes; see What an upgrade leaves behind
<file>.bak-<stamp>the file an upgrade replaced; see What an upgrade leaves behind
/var/backups/etcd/local etcd snapshots, unless spec.snapshots.dir sets another directory; pre-upgrade snapshots always go here. Local retention prunes only etcd-snapshot-<host>-*.db, and snapshot list shows only local files ending in .db; see Where snapshots go
/var/lib/stratum/log/<component>.loglogs of the supervised components; see Logs
/var/log/stratum/audit.logthe API server audit log, under the CIS profile. Records who made each request, not Secret values; see What the audit log records
/run/stratum/stratum.sockthe control socket (root only)
/run/stratum/containerd/containerd.sockthe CRI endpoint

Files Stratum writes outside its own directories

PathWrittenSee
/etc/systemd/system/stratum.serviceon systemd hostsReboot persistence
/etc/sysctl.d/99-stratum.confon every startHost settings
/etc/sysctl.d/99-stratum-cis.confunder the CIS profileHardening
/etc/modules-load.d/k8s.confon every startHost settings
/etc/containerd/certs.d/<registry>/hosts.tomlwhen registries.yaml has mirrorsRegistry mirrors
/etc/containerd/conf.d/stratum-registry.tomlwhen registries.yaml has mirrorsRegistry mirrors

Configuration keys

Under spec in /etc/stratum/config.yaml:

KeyDefaultSee
certRenewtrueCertificates
dashboard.enabledtrue while the operator runsThe dashboard
dashboard.nodePort30443; 0 for a ClusterIP onlyThe dashboard
dashboard.publicURLnoneThe dashboard
dashboard.tlsSecretNamenone: a certificate from the dashboard CAThe dashboard
dashboard.enableNodeShelltrue; false under cis: trueThe dashboard
dashboard.tokenSecretstrueThe dashboard
snapshots.intervalHours12Schedule settings
snapshots.disabledfalseSchedule settings
snapshots.dir/var/backups/etcd; a relative path or one with a .. element is ignoredSchedule settings
snapshots.retain5Where retention and the upload target come from
snapshots.s3noneWhere retention and the upload target come from

Kubernetes objects and labels

NameKindSee
stratum.ciq.com/control-plane=trueNode labelWhat a cluster upgrade creates
stratum.ciq.com/k8s-versionNode annotationWhat a cluster upgrade creates
stratum.ciq.com/versionNode annotationWhat a cluster upgrade creates
stratum.ciq.com/upgrade-in-progressNode annotationWhat a cluster upgrade creates
kube-system/stratum-cluster-upgradeLeaseWhat a cluster upgrade creates
stratum-upgrade-<node>Job, in kube-systemWhat a cluster upgrade creates
stratum.ciq.com/upgrade=<node>Job labelWhat a cluster upgrade creates
stratum.ciq.com/stack=<stack>label on objects applied from a manifest stackDeploying manifests
stratum-dashboardNamespace, Deployment and ServiceThe dashboard
stratum-dashboard/stratum-dashboard-tlsSecretThe dashboard
stratum-dashboard/stratum-dashboard-sessionSecretThe dashboard
kube-system/stratum-dashboard-caSecret, the dashboard's own CAThe dashboard
stratum-dashboard/stratum-dashboard-admin-token, stratum-dashboard-viewer-tokenSecret, sign-in tokensThe dashboard
stratum-dashboard-admin, stratum-dashboard-viewerServiceAccount and ClusterRoleBinding (cluster-admin, view)The dashboard

Timings and defaults

WhatValueSee
Leaf certificate lifetime365 daysCertificates
Automatic leaf rotationdaily check, rotates within 45 days of expiryCertificates
Scheduled snapshot interval12 hoursSchedule settings
Snapshots kept per control plane5Where retention and the upload target come from
Manifest deployer passevery 20 seconds; unchanged files re-applied every 5 minutesDeploying manifests
Cluster-upgrade lease60 seconds, renewed every 20What a cluster upgrade creates
Rollback wait before the health gate15 seconds (--soak)Restoring etcd with a rollback