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.

Sign up for GitHub

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

Jump to bottom

Operator - registry grpc healthcheck throws error when feast authorization is enabled #4848

Open
tchughesiv opened this issue Dec 12, 2024 · 0 comments · May be fixed by #4841
Open

Operator - registry grpc healthcheck throws error when feast authorization is enabled #4848

tchughesiv opened this issue Dec 12, 2024 · 0 comments · May be fixed by #4841
Labels
kind/bug priority/p2

Comments

@tchughesiv
Copy link
Contributor

Expected Behavior

The pods should start without issue

Current Behavior

The online and offline store pods will not start because the initContainer registry healthcheck never passes.
The registry throws this error -

File "/opt/app-root/lib64/python3.11/site-packages/feast/permissions/server/grpc_token_extractor.py", line 34, in extract_access_token
raise AuthenticationError("Missing authorization header")
starlette.authentication.AuthenticationError: Missing authorization header
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug priority/p2
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Improve operator service probes and add authz header grpc initContainer tchughesiv/feast
1 participant
@tchughesiv