-
Notifications
You must be signed in to change notification settings - Fork 179
Controller create ReplicationController with objectstore creds mount #397
Comments
The credentials are open only for slug build apps. The slugbuilder builds a slug from the git source and pushes into storage bucket which the slugrunner(app contianer) pull and runs it.So, the slugrunner needs to to know the creds of the storage for downloading the slug. |
Labeling as security as I know most administrators don't want their S3 credentials exposed to users. |
i think this deis/builder#138 should fix the issue. |
I don't think that's going to resolve the issue. The point being made here is that any buildpack application has direct access to the object store. That should not happen. I've also mentioned this previously in another issue: deis/controller#140 (comment) |
What i meant is we should have presigned urls so that the slug runner uses it to download and it need not have access to the creds.I have checked and currently s3, gcs and azure all support pre-signed urls. |
Ah I see what you mean. Apologies for the confusion. "Sign tarballs and compile slugs" doesn't exactly explain anything about migrating slugrunner to use presigned URLs for fetching slugs. |
+1 on pre-signed urls as currently I'm running into signature incompatibilities with The issue seems to be a long standing one: http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html |
this will be fixed with deis/controller#1179. |
closing as a duplicate of deis/slugrunner#58 which will be closed when deis/slugrunner#59 is merged. |
I was deploy application, deis create namespace for application and puth objectsotrage-keyfile secret to it:
Also deis create next RC for application:
So cluster swift credentials is open for any application? Is it a bug?
The text was updated successfully, but these errors were encountered: