← 返回首页
Kubernetes authorization manager should not use ClusterRoles · Issue #4623 · feast-dev/feast · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Resetting focus

Kubernetes authorization manager should not use ClusterRoles #4623

New issue
New issue

Description

Expected Behavior

Kubernetes authorization manager should rely only on Roles and RoleBindings defined in the namespace of the Feast service.

Current Behavior

Kubernetes authorization manager also fetches ClusterRoles which means that the Feast service must be granted cluster-wide privileges to inspect these instances.

Steps to reproduce

Install a Feast service in Kubernetes and enable the kubernetes authorization module.

Possible Solution

Use only Roles and RoleBindings defined in the namespace of the Feast service.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    • Open in GitHub Copilot app

    Footer

    © 2026 GitHub, Inc.