Skip to content

feat(ai-platform): add weaviate-service feature with Ray-optional reconcile path #80

Draft
kbhos-private wants to merge 6 commits intosplunk:mainfrom
kbhos-private:kiran/weekend-21-3
Draft

feat(ai-platform): add weaviate-service feature with Ray-optional reconcile path #80
kbhos-private wants to merge 6 commits intosplunk:mainfrom
kbhos-private:kiran/weekend-21-3

Conversation

@kbhos-private
Copy link

Description

This PR adds a new weaviate-service feature to AIPlatform so we can run a Weaviate proxy-only service without requiring Ray Serve. It also makes Ray reconciliation optional when the platform features do not need Ray, and wires RELATED_IMAGE_WEAVIATE_PROXY through operator manifests and Helm values.

Related Issues

  • Related to #

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test improvement
  • CI/CD improvement
  • Chore (dependency updates, etc.)

Changes Made

  • Added weaviate-service as a supported feature in API/CRD schema and feature registry.
  • Implemented new feature package: pkg/ai/features/weaviateservice (factory, reconciler logic, unit tests).
  • Made Ray optional in AIPlatform reconcile/setup flow:
  • Skip Ray watches when Ray CRDs are absent.
  • Skip Ray stages for Ray-independent feature sets.
  • Add Ray cleanup stage for weaviate-only mode.
  • Added RELATED_IMAGE_WEAVIATE_PROXY support in:

Testing Performed

  • Unit tests pass (make test)
  • Linting passes (make lint)
  • Integration tests pass (if applicable)
  • E2E tests pass (if applicable)
  • Manual testing performed

Test Environment

  • Kubernetes Version:
  • Cloud Provider:
  • Deployment Method:

Test Steps

  1. Build/deploy updated operator image and apply manifests/CRDs.
  2. Deploy AIPlatform with feature weaviate-service and verify creation for weaviate service.
  3. Verify weaviate-service pods/services become healthy and Ray resources are not required in weaviate-only mode.
    Run Go test suite locally:
    go test ./...

Documentation

  • Updated inline code comments
  • Updated README.md (if adding features)
  • Updated API documentation
  • Updated deployment guides
  • Updated CHANGELOG.md
  • No documentation needed

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have updated the Helm chart version (if applicable)
  • I have updated CRD schemas (if applicable)

Breaking Changes

Impact:
None expected.

Migration Path:
Migration Path: No mandatory migration. Existing saia/seca behavior remains; weaviate-service is additive.

Screenshots/Recordings

Additional Notes

Reviewer Notes

Please pay special attention to:


Commit Message Convention: This PR follows Conventional Commits

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.

2 participants