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

Adding e2e integration tests for feast go opertor #4792

Open
lokeshrangineni opened this issue Nov 25, 2024 · 3 comments
Open

Adding e2e integration tests for feast go opertor #4792

lokeshrangineni opened this issue Nov 25, 2024 · 3 comments
Labels
kind/feature New feature or request

Comments

@lokeshrangineni
Copy link
Contributor

lokeshrangineni commented Nov 25, 2024

Feast go operator is in development and we are creating this issue to track the effort to add e2e integration tests.

The goal of the ticket is to address following scenarios:

  1. Kubernetes FeatureStore CR should spin up all the necessary services required in our case it will be registry, online and offline services.
  2. Assert FeatureStore CR status should be in ready state.
  3. Assert registry, online and offline service pods are in Running state.
  4. Assert feast client ConfigMap is existing.
  5. Assert registry, online and offline services are having associated Kubernetes service objects defined.
  6. Assert registry, online and offline services are having associated Kubernetes service account objects defined.

Related Issues - 4561, 4783

@tchughesiv
Copy link
Contributor

let's get more specific about which e2e test(s)/scenarios are being added w/ this PR.

@lokeshrangineni
Copy link
Contributor Author

let's get more specific about which e2e test(s)/scenarios are being added w/ this PR.

I have updated the PR and Issue with specific details. Please let me know if I missed any other details.

@tchughesiv
Copy link
Contributor

assert FeatureStore CR conditions and phase are "ready" ... other status checks?

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

2 participants