This repository has been archived by the owner on Jul 3, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 114
Support deploying KuBOSH on AWS #98
Labels
Comments
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
Closed
Count me in when this is ready to developed. |
Merged
|
AWS scripts are in master. |
jhvhs
pushed a commit
that referenced
this issue
Aug 1, 2017
[#145602641][#98] Signed-off-by: Akshay Mankar <amankar@pivotal.io>
jhvhs
pushed a commit
that referenced
this issue
Aug 1, 2017
[#145602641][#98] Signed-off-by: Konstantin Semenov <ksemenov@pivotal.io>
jhvhs
pushed a commit
that referenced
this issue
Aug 1, 2017
* Also chown kubo-deployment instead of chmod 777 [#145602641][#98] Signed-off-by: Akshay Mankar <amankar@pivotal.io>
(closing) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rationale
Acceptance Criteria
kubo-deployment
repo and deploy KuBOSH in a AWS envThe text was updated successfully, but these errors were encountered: