-
Notifications
You must be signed in to change notification settings - Fork 30
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.
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
Provisioned disks for custom agent permission denied #741
Comments
I can confirm that setting |
Dobosz
added a commit
to Dobosz/langstream
that referenced
this issue
Dec 11, 2023
@Dobosz I saw you pushed the commit in your fork, can you open a PR? the change LGTM and I'd do the same fix |
Dobosz
added a commit
to Dobosz/langstream
that referenced
this issue
Dec 11, 2023
eolivelli
pushed a commit
that referenced
this issue
Dec 11, 2023
Dobosz
added a commit
to Dobosz/langstream
that referenced
this issue
Dec 13, 2023
…ign to Agent STS and not App
Dobosz
added a commit
to Dobosz/langstream
that referenced
this issue
Dec 14, 2023
…ign to Agent STS and not App
nicoloboschi
pushed a commit
that referenced
this issue
Dec 14, 2023
benfrank241
pushed a commit
to vectorize-io/langstream
that referenced
this issue
May 2, 2024
benfrank241
pushed a commit
to vectorize-io/langstream
that referenced
this issue
May 2, 2024
* Revert "[Issue LangStream#741] Add fsGroup for runtime pod (LangStream#743)" This reverts commit 2cd631c. * [Issue LangStream#741] Fixes previous commit. fsGroup will now be assign to Agent STS and not App
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Custom agent running on stateful set mounts volume with
755
and is owned byid=0
. Since container is running on userid=10000
there is no write permission on mounted disk. I understand this is not desired behaviour.Agent description:
Runtime
My runtime is GCP GKE cluster version
1.27.5-gke.200
running on autopilot. Thedefault
storage class is as follows:It's probably a GKE specific issue, but I've not tested it yet on other runtime yet.
The text was updated successfully, but these errors were encountered: