You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we support pushing and getting logs , caches and artifacts from the blob storage configured in the cluster where devtron is installed but when I'm using system executor, we should let people push and get logs, caches and artifacts in external cluster env in blob storage configured in ext cluster.
🎤 Pitch
We can expect from a user that they have given us a config map and secret with a particular name, in which we can provide the cloud provider and blob storage credentials then we can read them to upload and get all the artifacts to that blob storage configured in ext cluster
✌️ Solution
I want the logs, caches and artifacts of pre/post cd and jobs to be pushed in blob storage configured in external cluster, so that a user can have independent choice of if they ran any pre/post cd or job in ext env then it's only logical for them to use the blob storage configured in that cluster only rather than the blob storage that is configured where devtron is installed.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🔖 Feature description
Currently, we support pushing and getting logs , caches and artifacts from the blob storage configured in the cluster where devtron is installed but when I'm using system executor, we should let people push and get logs, caches and artifacts in external cluster env in blob storage configured in ext cluster.
🎤 Pitch
We can expect from a user that they have given us a config map and secret with a particular name, in which we can provide the cloud provider and blob storage credentials then we can read them to upload and get all the artifacts to that blob storage configured in ext cluster
✌️ Solution
I want the logs, caches and artifacts of pre/post cd and jobs to be pushed in blob storage configured in external cluster, so that a user can have independent choice of if they ran any pre/post cd or job in ext env then it's only logical for them to use the blob storage configured in that cluster only rather than the blob storage that is configured where devtron is installed.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#6541
The text was updated successfully, but these errors were encountered: