Skip to content
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

Feature: logs, caches and artifacts ran in external cluster env must get pushed in blob storage configured in ext cluster #4184

Closed
2 tasks done
prakash100198 opened this issue Oct 31, 2023 · 0 comments · Fixed by #4138 or devtron-labs/ci-runner#108
Assignees
Labels
enhancement New feature or request

Comments

@prakash100198
Copy link
Contributor

prakash100198 commented Oct 31, 2023

🔖 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?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

AB#6541

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment