You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To use the the new fine-grained AWS IAM roles for service accounts feature with the default pre-packaged servers SeldomDeployment example, the ServiceAccountName ( defining a service account that have the new eks.amazonaws.com/role-arn annotation like defined here https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/) needs to be passed to the generated initContainer (or any of the container in the pod).
The eks annotation doesn't work if the SeldonDeployment is defined like in the documentation here:
This is because the serviceAccountName is used to in model_initializer_injector.go controller to get the secrets defined in the Service Account only and doesn't attach it to the containers itself so that EKS can do its magic...
The workaround for now is to explicitly define all the containers and use the v0.3.0 or above of gcr.io/kfserving/storage-initializer (example below). It would be nice to keep using the pre-packaged servers with this new feature.
To use the the new fine-grained AWS IAM roles for service accounts feature with the default pre-packaged servers SeldomDeployment example, the
ServiceAccountName
( defining a service account that have the neweks.amazonaws.com/role-arn
annotation like defined here https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/) needs to be passed to the generated initContainer (or any of the container in the pod).The eks annotation doesn't work if the SeldonDeployment is defined like in the documentation here:
This is because the
serviceAccountName
is used to inmodel_initializer_injector.go
controller to get the secrets defined in the Service Account only and doesn't attach it to the containers itself so that EKS can do its magic...The workaround for now is to explicitly define all the containers and use the v0.3.0 or above of
gcr.io/kfserving/storage-initializer
(example below). It would be nice to keep using the pre-packaged servers with this new feature.The text was updated successfully, but these errors were encountered: