We are pleased to announce the release of KubeDB v2023.01.31 . This post lists all the major changes done in this release since the last release.
The release was mainly focus on some hot fix regarding
Private Registry ImagePull, Postgres
pg-coordinator leader switch issue and running Kibana and OpenSearch dashboard as
non root user.
You can find the detailed changelogs here .
Private Registry ImagePull
We have faced issues related to pulling image from
insecure registry.Now you can specify the image-pull secret for the private registry and register the insecure registry while installing / upgrading kubeDB.
Operator will use that plus any image pull secret in the
db.spec.podTemplate to get the docker image digest.
kubectl create secret docker-registry regcred \ --namespace kubedb \ --docker-server=<your-registry-server> \ --docker-username=<your-name> \ --docker-password=<your-pword>
helm install kubedb appscode/kubedb \ --version v2023.01.31 \ --namespace kubedb --create-namespace \ --set kubedb-provisioner.enabled=true \ --set kubedb-ops-manager.enabled=true \ --set kubedb-autoscaler.enabled=true \ --set kubedb-dashboard.enabled=true \ --set kubedb-schema-manager.enabled=true \ --set-file global.license=/path/to/the/license.txt\ --set global.imagePullSecrets.name=regcred --set global.insecureRegistries=harbor.example.com
Pg-coordinator Leader Switch
Pg-coordinator leader switch issue is addressed in this release.From this release KubeDB managed High Availability PostgreSQL will be stable more than before. Try out kubedb manged PostgreSQL
Kibana and Opensearch Dashboard As non-root user
Kibana and Opensearch-Dashboards init container docker images will be using Non-root user. Running the Docker containers as a non-root user eliminates potential vulnerabilities in the daemon and the container runtime. This is because if a user manages to break out of the application running as root in the container, he may gain root user access on the host. In addition, configuring a container to user unprivileged is the best way to prevent privilege escalation attacks. You can try out Deploy Kibana With ElasticsearchDashboard
Please try the latest release and give us your valuable feedback.
If you want to install KubeDB, please follow the installation instruction from here .
If you want to upgrade KubeDB from a previous version, please follow the upgrade instruction from here .
To speak with us, please leave a message on our website .
To join public discussions with the KubeDB community, join us in the Kubernetes Slack team
#kubedb. To sign up, use our Slack inviter
To receive product announcements, follow us on Twitter .
If you have found a bug with KubeDB or want to request for new features, please file an issue .