Conversation
|
@chinochao Thanks for the PR! Ultimately, we intend to nest parameters like these under With eda-server-operator, we have the luxury of a fresh start and can do this now. Would you be open to re-working the PR? The user could then define it on the EDA spec like this: We'll also need CRD and CSV entries, like these, but nested under |
|
@chinochao I was trying to reproduce the actual bug first while testing this out but could not while using k3s locally. Could you share more details about your deployment? It'd be good to know under what circumstances this permissions error might occur, so that we can document the fix better. |
|
you can reproduce this with deployment on EKS with gp2 storage class (based on aws-ebs) |
|



Adding the option to add custom security context for Postgres as in K8s it does not start due to a permission issue. This allows to change the user id, group id, etc to anything other than 26 used by the image https://quay.io/repository/sclorg/postgresql-13-c9s
#138
Example usage: