Repository navigation
Releases
Releases · curityio/curity-operator
0.0.1
Curity Kubernetes Operator — initial release 🎉
This is the first public release of the Curity Kubernetes Operator, which deploys and manages the
Curity Identity Server on Kubernetes using declarative custom resources.
Highlights
- Three custom resources to model a deployment:
IdentityServerCluster(isc) — cluster-wide settings: Curity version, admin credentials, logging, scheduling defaults, packages and observabilityIdentityServerNode(isn) — admin and runtime nodes, each backed by a managed Deployment and ServiceIdentityServerDatabase(isdb) — database schema management through Kubernetes Jobs
- Configuration management — the operator discovers labeled ConfigMaps and Secrets (base configuration,
licenses, post-commit scripts), mounts them into the right nodes, and triggers safe rolling restarts when they change - Custom plugin packages — fetch plugin/package ZIP archives from remote URLs, with support for private
endpoints (bearer/basic auth) and custom TLS trust - Production features — horizontal pod autoscaling, PodDisruptionBudgets, NetworkPolicies, Prometheus
ServiceMonitorintegration, and TLS keystore conversion handled by the operator - Strong validation — extensive CEL validation rules on the CRDs catch invalid specs at admission time
- Multi-arch image —
linux/amd64andlinux/arm64, based on Red Hat UBI 9 minimal, running as non-root
Installation
The operator image and Helm chart are published to curity.azurecr.io:
helm install curity-operator oci://curity.azurecr.io/charts/curity-operator
--namespace curity-operator --create-namespace
Alternatively, apply the plain manifests attached to this release:
kubectl apply -f https://github.com/curityio/curity-operator/releases/0.0.1/download/install.yaml
See the README for prerequisites, chart values,
and a full reference of the custom resources, plus example manifests to get a cluster running.
Compatibility
- Kubernetes 1.25 or later (the CRDs rely on CEL validation rules)
- The CRD API group is currently
v1alpha1: the resources are fully functional, but the API surface
may still change in backwards-incompatible ways before it graduates. Breaking changes will be called
out in the release notes.
Feedback
Issues and feature requests are welcome on the issue tracker.