Operator E2E Test to cover the FeatureStore customer resource with remote registry.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
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
Metadata
Metadata
Labels
No fields configured for issues without a type.
Development
No branches or pull requests