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

feat: Adding first basic feast operator e2e test. #4791

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

lokeshrangineni
Copy link
Contributor

@lokeshrangineni lokeshrangineni commented Nov 25, 2024

Adding first basic feast operator e2e test.

Issue we are fixing: 4792

@lokeshrangineni lokeshrangineni changed the title Adding first basic feast operator e2e test. feat: Adding first basic feast operator e2e test. Nov 25, 2024
@lokeshrangineni lokeshrangineni marked this pull request as ready for review November 25, 2024 21:04
@lokeshrangineni lokeshrangineni requested a review from a team as a code owner November 25, 2024 21:04
_, err = utils.Run(cmd)
ExpectWithOffset(1, err).NotTo(HaveOccurred())

var feastImage = "example.com/feature-transformation-server:operator.v0"
By("loading the the feast image on Kind")
var feastImage = "feastdev/feature-server:dev"
Copy link
Contributor

Choose a reason for hiding this comment

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

to be sure that k8s is looking locally and not trying to pull from a repo...

Suggested change
var feastImage = "feastdev/feature-server:dev"
var feastImage = "localhost/feastdev/feature-server:dev"

registry:
local:
# This image is expected to build and to be available in the CI or when you run `make feast-ci-dev-docker-img`
image: 'feastdev/feature-server:dev'
Copy link
Contributor

Choose a reason for hiding this comment

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

same

Copy link
Contributor

@tchughesiv tchughesiv left a comment

Choose a reason for hiding this comment

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

Don't forget to add checks around the FeatureStore CR status... checking ready state and individual feast service type conditions. Feel free to add whatever other CR status checks you think would be valuable. Generally, the more we test the better ... will help ensure a stable release.

// Get pod name

cmd := exec.Command("kubectl", "get",
"pods", "-l", "feast.dev/service-type=registry",
Copy link
Contributor

Choose a reason for hiding this comment

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

i wonder if the better route might be to check the registry deployment object and wait for availability condition to be true. this will allow for easier testing around scaling later when we add that capability.


cmOutput, err := utils.Run(cmd)
ExpectWithOffset(2, err).NotTo(HaveOccurred())
configMap := utils.GetNonEmptyLines(string(cmOutput))
Copy link
Contributor

Choose a reason for hiding this comment

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

it would be good to validate the contents of the client configmap are as expected

Comment on lines +7 to +8
services:
registry:
Copy link
Contributor

Choose a reason for hiding this comment

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

we should test all 3 service types with this PR... onlineStore and offlineStore should be added

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants