-
Notifications
You must be signed in to change notification settings - Fork 78
Simplify handling of storage configuration and IPs #229
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
hi @mcopik can I pick this up? |
@ojninja16 Sure! it shouldn't be difficult - look through our instructions and simplify the storage handling :) |
hi @mcopik can you give me some more context regarding the requirements of this issue, so I can get started with it |
@ojninja16 Thanks for the interest! (I'm also checking the other PR you contributed, which should be merged soon.) For this issue, we are referring to the documentation that describes the process of setting up for storage on OpenWhisk (same applies to Fission and Knative in pending PRs). Right now, we expect the user to manually change JSON config and replace this part in the main config or provide updated storage configuration via My suggestion for a simple improvement should be to not require users to manually run Please feel invited to join us on Slack - discussion will be easier there :) Invitation link |
Understood ,Cool! thanks for the invite 🙏 |
Currently, Kubernetes-based platforms require special treatment - storage needs to be deployed by the user. Documentation recommends using the manual
jq
command to input storage configuration, but we have recently added a CLI flag to simplify this process.In future, we should handle it completely automatically and offer a CLI flag to just replace the IP address when needed.
The text was updated successfully, but these errors were encountered: