Releases: ydb-platform/ydb-kubernetes-operator
Releases · ydb-platform/ydb-kubernetes-operator
0.6.4
v0.6.4 - 2025-05-21
Added
insecurePortcan be specified in GRPC Service spec to create a Service with a second port (for non-tls grpc port in storage)- Default 2135 port on the GRPC service can now be overridden
 
Fixed
- [development] mutating\validating webhooks now run during medium tests (previously e2e only)
 
Docker images
New docker images are available from:
- ydbplatform/ydb-kubernetes-operator:0.6.4
 - cr.yandex/yc/ydb-kubernetes-operator:0.6.4
 
Helm charts
New helm chart 'ydb-operator', version 0.6.4 is available from https://charts.ydb.tech
0.6.3
v0.6.3 - 2025-05-07
Fixes
operatorSyncoption could not be set to false when spec.configuration field is an unsorted YAML
Docker images
New docker images are available from:
- ydbplatform/ydb-kubernetes-operator:0.6.3
 - cr.yandex/yc/ydb-kubernetes-operator:0.6.3
 
Helm charts
New helm chart 'ydb-operator', version 0.6.3 is available from https://charts.ydb.tech
0.6.2
v0.6.2 - 2025-02-24
Fixed
- bug: regression with pod name in grpc-public-host arg
 
Docker images
New docker images are available from:
- ydbplatform/ydb-kubernetes-operator:0.6.2
 - cr.yandex/yc/ydb-kubernetes-operator:0.6.2
 
Helm charts
New helm chart 'ydb-operator', version 0.6.2 is available from https://charts.ydb.tech
0.6.1
v0.6.1 - 2025-02-12
Fixed
- fix passing interconnet TLS volume in blobstorage-init job
 
Docker images
New docker images are available from:
- ydbplatform/ydb-kubernetes-operator:0.6.1
 - cr.yandex/yc/ydb-kubernetes-operator:0.6.1
 
Helm charts
New helm chart 'ydb-operator', version 0.6.1 is available from https://charts.ydb.tech
0.6.0
v0.6.0 - 2025-01-29
Added
- starting with this release, deploying to dockerhub (ydbplatform/ydb-kubernetes-operator)
 - added the ability to create metadata announce for customize dns domain (default: cluster.local)
 - new field additionalPodLabels for Storage and Database CRD
 - new method buildPodTemplateLabels to append additionalPodLabels for statefulset builders
 - compatibility tests running automatically on each new tag
 - customize Database and Storage container securityContext
 - field externalPort for grpc service to override --grpc-public-port arg
 - annotations overrides default secret name and key for arg --auth-token-file
 - field ObservedGeneration inside .status.conditions
 
Changed
- up CONTROLLER_GEN_VERSION to 0.16.5 and ENVTEST_VERSION to release-0.17
 - refactor package labels to separate methods buildLabels, buildSelectorLabels and buildeNodeSetLabels for each resource
 - propagate labels ydb.tech/database-nodeset, ydb.tech/storage-nodeset and ydb.tech/remote-cluster with method makeCommonLabels between resource recasting
 
Fixed
- e2e tests and unit tests flapped because of the race between storage finalizers and uninstalling operator helm chart
 - regenerate CRDs in upload-artifacts workflow (as opposed to manually)
 - additional kind worker to maintain affinity rules for blobstorage init job
 - update the Makefile with the changes in GitHub CI
 - bug: missing error handler for arg --auth-token-file
 - fix field resourceVersion inside .status.remoteResources.conditions
 - panic when create object with .spec.pause is true
 - Passing additional secret volumes to blobstorage-init. The init container can now use them without issues.
 
Security
- bump golang-jwt to v4.5.1 (by dependabot)
 - bump golang.org/x/net from 0.23.0 to 0.33.0 (by dependabot)
 
0.5.32
v0.5.32 - 2024-11-05
Fixed
- Chart.yaml version is bumped up automatically when a new release PR is created
 
Docker images
New docker images are available from:
- cr.yandex/yc/ydb-kubernetes-operator:0.5.32
 
Helm charts
New helm chart 'ydb-operator', version 0.5.32 is available from charts.ydb.tech.
YDB Kubernetes operator 0.4.19-alpha
This is the first release. Going forward we'll keep a changelog in the form of releases!
Bug fixes:
- Fixed Storage resource flapping on creation between 
ProvisioningandInitializingstates, by @Jorres in #101 
New Contributors
- @bma13 made their first contribution in #43
 - @mvgorbunov made their first contribution in #53
 - @asmyasnikov made their first contribution in #78
 - @shmel1k made their first contribution in #82