-
Notifications
You must be signed in to change notification settings - Fork 996
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
Add Dockerfile for GCP CloudRun FeatureServer #1887
Conversation
Hi @judahrand. Thanks for your PR. I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov Report
@@ Coverage Diff @@
## master #1887 +/- ##
==========================================
- Coverage 81.89% 80.39% -1.51%
==========================================
Files 97 99 +2
Lines 7756 9345 +1589
==========================================
+ Hits 6352 7513 +1161
- Misses 1404 1832 +428
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/ok-to-test |
Hey @judahrand, thanks for this PR! We're currently working on serverless deployments on AWS Lambda, so a few things will likely be changing over the next couple of weeks (e.g. in the |
Works for me! Happy to rework this then if need be. |
Great, thanks @judahrand. I'll let you know when the AWS serverless changes have landed. |
execution_role_name: StrictStr | ||
"""The execution role for the AWS Lambda function.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably don't need this for gcp?
enabled: StrictBool = False | ||
"""Whether the feature server should be launched.""" | ||
|
||
public: StrictBool = True | ||
"""Whether the endpoint should be publicly accessible.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these used anywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
store = FeatureStore(repo_path=str(repo_path.resolve())) | ||
|
||
# Create the FastAPI app | ||
app = get_app(store) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the only diff between this and the aws lambda app the fact that that one uses mangum?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I believe that is the only difference in the app.py
file.
154f711
to
9c3e1c9
Compare
Signed-off-by: Judah Rand <17158624+judahrand@users.noreply.github.com>
fafdc80
to
041b0e4
Compare
Signed-off-by: Judah Rand <17158624+judahrand@users.noreply.github.com>
Signed-off-by: Judah Rand <17158624+judahrand@users.noreply.github.com>
041b0e4
to
0892133
Compare
@achals Failures don't look like my fault |
yeah i fixed these (integ test clean up issue). Can you remove the role name field from the gcp config? Should be g2g after that. |
I did, didn't I? 🤔 Do you mean something other than what I removed? |
Oh oops I was looking at an older version of the PR. You did, my bad. |
Shouldn't dockerfiles be in https://github.com/feast-dev/feast/tree/master/infra/docker? |
🤷 I just followed the pattern 😛 The AWS one lives in the equivalent place at the moment. I kinda think this is okay. Otherwise, the resources for the Feature Server cloud deployments will get spread out and more difficult to work on. |
Also I think the answer here is no as my understanding is that these Dockerfiles are part of the SDK. There are needed in order to locally build the images and push them to the user's registry. |
@achals Do you think this is worth merging and then working on the other bits needed to complete the CloudRun support? (The failed test looks like a timeout) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: felixwang9817, judahrand The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
/kind feature |
Hey @judahrand, your changes lgtm but for some reason integration tests are failing (doesn't seem to be due to your changes). I'm going to take a look and see if I fix the integration test failures. Edit: nvm, looks like your changes have been merged. |
It looked like a timeout when I looked briefly - job was cancelled rather than failure iirc. |
What this PR does / why we need it:
Pretty self explanatory.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: