-
Notifications
You must be signed in to change notification settings - Fork 159
Improve Deployment Scripts #37
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
Comments
Ideally the user can run 1 script for an End to End deployment, that checks whether things (service account, role bindings, json keys) already exist, and if not, creates them, then is able to deploy the driver. And maybe even clean up the key from the machine afterwards. |
/cc @msau42 Does this seem like a reasonable thing to do ^ |
Sure sounds reasonable |
Should the default namespace be default? Or would it be better to have a GCE PD specific namespace? |
Better to have a special namespace just for the driver |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
namespace shouldn't be configurable, actually will just be set directly |
STOR-1163: Rebase to upstream v1.10.1
The text was updated successfully, but these errors were encountered: