Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operator E2E Test to cover the FeatureStore customer resource with remote registry. #4823

Open
lokeshrangineni opened this issue Dec 6, 2024 · 0 comments
Labels
kind/feature New feature or request

Comments

@lokeshrangineni
Copy link
Contributor

lokeshrangineni commented Dec 6, 2024

This is an extended issue to 4792

We have to add the operator E2E test to cover following scenario.

  • Deploy the feature store custom resource in one of of the kubernetes namespace.
  • Deploy the another feature store custom resource in another namespace but should point to the registry using remote setting which should refer to the registry service created in the previous step.
  • Assert all the conditions mentioned in the ticket-4792
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant