-
Notifications
You must be signed in to change notification settings - Fork 3
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
Deploy storage broker #1
Comments
This one is not so easy to untangle: https://github.com/RedHatInsights/insights-storage-broker/blob/master/deploy/clowdapp.yml I'd like to deploy it without logging to a bucket and without multiple kafka topics at first.... |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/assign @mimotej as noted above, we need to deploy Spec for the clowder options can be found here: https://github.com/RedHatInsights/insights-storage-broker/blob/879a1d977af6783281ab229a8fcd97421a1f5e72/src/storage_broker/utils/config.py#L34-L60 using Clowder Python library: https://github.com/RedHatInsights/app-common-python Consider dependency on Note: please do not use https://github.com/RedHatInsights/insights-storage-broker/blob/master/templates/deployment.yml, as we want to deploy the config as it is defined in ClowderApp. Investigate use of S3 credentials in storage broker, since it seems they may be using the same credentials for all buckets - this may be problematic in ODF. Use: https://github.com/RedHatInsights/insights-storage-broker/blob/879a1d977af6783281ab229a8fcd97421a1f5e72/default_map.yaml#L1-L2 only, we are not validating OpenShift payloads for now. |
seraph is currently on hold |
No description provided.
The text was updated successfully, but these errors were encountered: