Kapitan generator releases, 9 to 15 November 2026
New Kapitan generator versions on kadet-hub from 9 to 15 November 2026: ironcore, keycloak, multus, prometheus-operator, rook-ceph, strimzi, terraform-aws,…
Versions published on kadet-hub from 9 to 15 November 2026, each through the gate and signed. The generator page shows each version’s output diff against the version before it, its SBOM and the command that verifies it.
| Generator | Versions | Changes |
|---|---|---|
| ironcore | 1.0.3 | CHANGELOG |
| keycloak | 1.1.2 | CHANGELOG |
| multus | 1.0.4 | CHANGELOG |
| prometheus-operator | 1.1.7 | CHANGELOG |
| rook-ceph | 1.0.4 | CHANGELOG |
| strimzi | 1.1.2 | CHANGELOG |
| terraform-aws | 0.1.5 | CHANGELOG |
| terraform-azurerm | 0.1.5 | CHANGELOG |
| terraform-google | 0.1.5 | CHANGELOG |
| terraform-opentelekomcloud | 0.1.4 | CHANGELOG |
ironcore
ironcore 1.0.3
Built for IronCore 0.9.0. The breaking changes of the release are in the IRI runtime API, etcd and the Kubernetes Go libraries. The generated OpenAPI v3 documents of the compute, networking and storage groups are the same as at v0.8.0, so the shipped schemas and rendered output are unchanged. The validation and defaulting files the README cites are unchanged at v0.9.0, and their links move to that tag.
keycloak
keycloak 1.1.2
Built for Keycloak Operator 26.8.2. The CRDs and their JSON Schemas are unchanged from 26.8.1, as is the operator code the generator’s defaults rely on. The upstream files the README cites are unchanged at 26.8.2, and their links move to that tag. Rendered output is unchanged.
multus
multus 1.0.4
Built for Multus CNI 4.3.2. Its NetworkAttachmentDefinition CRD is unchanged, so the shipped schema and rendered output are unchanged. Multus 4.3.2 still builds with network-attachment-definition-client v1.7.6. Of the Multus files the README cites, only docs/how-to-use.md changes at v4.3.2, by a --force-config-watch section outside the cited one, and their links move to that tag.
prometheus-operator
prometheus-operator 1.1.7
Built for Prometheus Operator 0.95.1. Its CRDs add fields and remove none, and their kinds, versions and short names are unchanged, so the flat keys, shorthands and output keys still apply. New fields such as extraScrapeMetrics on Prometheus, PrometheusAgent, ServiceMonitor, PodMonitor, Probe and ScrapeConfig, or alertmanagerConfigFileSystemMode on Alertmanager, go into spec. In the CRDs, clientAuthType of web.tlsConfig and of Alertmanager clusterTLS.server only accepts the five Go tls.ClientAuthType names. A Webex receiver in an AlertmanagerConfig needs httpConfig.authorization or httpConfig.bearerTokenSecret. With alertmanagerConfigFileSystemMode and alertmanagerConfigMatcherStrategy unset, the operator now rejects an AlertmanagerConfig that references a file in the Alertmanager container, such as a Telegram botTokenFile, unless alertmanagerConfiguration names it. The upstream files the README cites say the same at v0.95.1, and their links move to that tag. The kube-prometheus-stack links move to chart 93.1.1, the newest that ships 0.95.1. The selector values and template lines the README cites are the same as in 92.3.0. Rendered output is unchanged.
rook-ceph
rook-ceph 1.0.4
Built for Rook 1.21.2. Its deploy/examples/crds.yaml is the same file as at 1.21.1, so the shipped schemas and CRDs and the rendered output are unchanged. The upstream files the README cites are unchanged at v1.21.2 apart from spec.go, where the cited code is the same but now at lines 198 to 204. Their links move to that tag. The example Ceph image is still quay.io/ceph/ceph:v20.2.4.
strimzi
strimzi 1.1.2
Built for Strimzi 1.3.1. Its Kafka, KafkaNodePool, KafkaTopic and KafkaUser CRDs are unchanged, so the shipped schemas and rendered output are unchanged. Strimzi 1.3.1 adds Kafka 4.3.2 and makes it the default, which the Cluster Operator uses for a Kafka entry without version. The upstream files and documentation pages the README and the code comments cite differ at 1.3.1 only in Strimzi, Kafka and Bridge versions, and their links move to that tag.
terraform-aws
terraform-aws 0.1.5
Pins hashicorp/aws 6.72.0 instead of 6.71.0 in providers.tf.json and ships its provider schema extract under schemas/terraform/, so the catalog shows “Built for hashicorp/aws 6.72.0”. The extracts of both versions are the same, and the 6.72.0 release notes change none of the 15 resource types the generator emits. Rendered output differs only in the provider version.
terraform-azurerm
terraform-azurerm 0.1.5
Pins hashicorp/azurerm 5.13.0 instead of 5.12.0 in providers.tf.json and ships its provider schema extract under schemas/terraform/, so the catalog shows “Built for hashicorp/azurerm 5.13.0”. Of the seven resource types the generator emits, the 5.13.0 release notes name only azurerm_storage_account. It gains the optional smb_oauth_enabled, which the generator does not set and which is the only difference between the two extracts. Its customer_managed_key check now also accepts FileStorage accounts on the V2 billing model, and the generator emits StorageV2 accounts without a customer-managed key. Of the resource sources of the seven types only storage_account_resource.go changes, for these two entries. Rendered output differs only in the provider version.
terraform-google
terraform-google 0.1.5
Pins hashicorp/google 8.10.0 instead of 8.9.0 in providers.tf.json and ships its provider schema extract under schemas/terraform/, so the catalog shows “Built for hashicorp/google 8.10.0”. The extracts of both versions are the same, and the 8.10.0 release notes name none of the seven resource types the generator emits. Rendered output differs only in the provider version.
terraform-opentelekomcloud
terraform-opentelekomcloud 0.1.4
Pins opentelekomcloud/opentelekomcloud 1.37.12 instead of 1.37.11 in providers.tf.json and ships its provider schema extract under schemas/terraform/, so the catalog shows “Built for opentelekomcloud/opentelekomcloud 1.37.12”. The extracts of both versions are the same, and the 1.37.12 release notes name none of the seven resource types the generator emits. Rendered output differs only in the provider version.