Skip to content

Conversation

@ZobayerAbedin
Copy link
Member

No description provided.

@CLAassistant
Copy link

CLAassistant commented Oct 16, 2025

CLA assistant check
All committers have signed the CLA.

@gitguardian
Copy link

gitguardian bot commented Dec 5, 2025

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@Neaj-Morshad-101 Neaj-Morshad-101 marked this pull request as ready for review December 5, 2025 12:18
Copilot AI review requested due to automatic review settings December 5, 2025 12:18
Copilot finished reviewing on behalf of Neaj-Morshad-101 December 5, 2025 12:19
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request updates various Kubernetes and KubeDB dependencies to newer versions and introduces schema enhancements across multiple Custom Resource Definitions (CRDs). Despite the title "HanaDB", the changes primarily involve dependency version bumps and standardization of CRD schemas across the KubeDB ecosystem, including the addition of two new database types (Weaviate and Qdrant).

Key Changes:

  • Bumped Kubernetes dependencies from v0.32.3 to v0.32.8
  • Updated KubeDB apimachinery from v0.58.0 to v0.59.1-0.20251205110528-3d10db600e5d
  • Standardized authSecret schema by making kind and name required fields with defaults
  • Added new vector database support (Weaviate and Qdrant CRDs)
  • Introduced maxRetries field with default value 1 across all ops request CRDs
  • Enhanced functionality with monitoring, ACL, tuning, and TCPS configuration options

Reviewed changes

Copilot reviewed 29 out of 214 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
vendor/modules.txt Version bumps for k8s.io (v0.32.3→v0.32.8), kmodules.xyz, kubedb.dev/apimachinery, and kubeops.dev/petset dependencies
vendor/kubeops.dev/petset/ Added monitoring configuration support in PlacementPolicy and updated deepcopy generation
vendor/kubedb.dev/apimachinery/crds/ops.kubedb.com_*opsrequests.yaml Added maxRetries field (default: 1) and standardized secretRef structure with required kind and name fields across all database ops requests
vendor/kubedb.dev/apimachinery/crds/kubedb.com_weaviates.yaml New CRD for Weaviate vector database support (3419 lines)
vendor/kubedb.dev/apimachinery/crds/kubedb.com_qdrants.yaml New CRD for Qdrant vector database support (3423 lines)
vendor/kubedb.dev/apimachinery/crds/kubedb.com_*s.yaml Standardized authSecret schema, removed .apiVersion printer columns, added database-specific features (Redis ACL, Postgres tuning, Kafka broker rack, Oracle TCPS)
vendor/kubedb.dev/apimachinery/crds/gitops.kubedb.com_*.yaml Applied same authSecret schema standardization and feature additions to GitOps CRDs
vendor/kubedb.dev/apimachinery/crds/kafka.kubedb.com_connectclusters.yaml Standardized authSecret schema consistent with other CRDs

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Signed-off-by: ZobayerAbedin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants