Skip to content

feat: OIDC authorization in Feast Operator #4801

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

Merged
dmartinol merged 11 commits into from
Dec 4, 2024
Merged

feat: OIDC authorization in Feast Operator #4801

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
7f5c5bb
Initial commit
dmartinol Nov 22, 2024
55badf9
no private image
dmartinol Nov 22, 2024
2453a11
removed nameLabelKey, using serices.NameLabelKey
dmartinol Nov 25, 2024
cad9f3e
improved CRD comments and using IsLocalRegistry
dmartinol Nov 25, 2024
25f1d90
fixing generated code
dmartinol Nov 25, 2024
2579f40
renamed auth condition and types
dmartinol Nov 26, 2024
acde71a
more renamings
dmartinol Nov 26, 2024
82085d6
initial commit
dmartinol Nov 28, 2024
99455e5
oidc IT
dmartinol Dec 2, 2024
5f2fd33
with sample
dmartinol Dec 2, 2024
e3de29c
no private image
dmartinol Dec 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fixing generated code 
Signed-off-by: Daniele Martinoli <dmartino@redhat.com>
  • Loading branch information
@dmartinol
dmartinol committed Dec 3, 2024
commit 25f1d90853ecb8fc7ac9544ba12d5248cbb6ccbc
22 changes: 12 additions & 10 deletions infra/feast-operator/dist/install.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,16 +62,17 @@ spec:
properties:
kubernetes:
description: |-
KubernetesAuth defines the authorization settings using Kubernetes RBAC.
KubernetesAuth provides a way to define the authorization settings using Kubernetes RBAC resources.
https://kubernetes.io/docs/reference/access-authn-authz/rbac/
properties:
roles:
description: |-
The Kubernetes RBAC roles to be deployed in the same namespace of the FeatureStore.
See the Feast permission model https://docs.feast.dev/getting-started/concepts/permission
Please note that the feature store admin is not obligated to manage roles using the Feast operator.
Roles can be managed independently. This configuration is only providing a way to automate this step.
Note that the operator cannot ensure that these roles will match the ones used in the configured Feast permissions.
Roles are managed by the operator and created with an empty list of rules.
See the Feast permission model at https://docs.feast.dev/getting-started/concepts/permission
The feature store admin is not obligated to manage roles using the Feast operator, roles can be managed independently.
This configuration option is only providing a way to automate this procedure.
Important note: the operator cannot ensure that these roles will match the ones used in the configured Feast permissions.
items:
type: string
type: array
Expand Down Expand Up @@ -1230,16 +1231,17 @@ spec:
properties:
kubernetes:
description: |-
KubernetesAuth defines the authorization settings using Kubernetes RBAC.
KubernetesAuth provides a way to define the authorization settings using Kubernetes RBAC resources.
https://kubernetes.io/docs/reference/access-authn-authz/rbac/
properties:
roles:
description: |-
The Kubernetes RBAC roles to be deployed in the same namespace of the FeatureStore.
See the Feast permission model https://docs.feast.dev/getting-started/concepts/permission
Please note that the feature store admin is not obligated to manage roles using the Feast operator.
Roles can be managed independently. This configuration is only providing a way to automate this step.
Note that the operator cannot ensure that these roles will match the ones used in the configured Feast permissions.
Roles are managed by the operator and created with an empty list of rules.
See the Feast permission model at https://docs.feast.dev/getting-started/concepts/permission
The feature store admin is not obligated to manage roles using the Feast operator, roles can be managed independently.
This configuration option is only providing a way to automate this procedure.
Important note: the operator cannot ensure that these roles will match the ones used in the configured Feast permissions.
items:
type: string
type: array
Expand Down