-
Notifications
You must be signed in to change notification settings - Fork 217
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
feat(capture): add managed storage account support #575
Conversation
Signed-off-by: Qingchuan Hao <[email protected]>
Signed-off-by: Qingchuan Hao <[email protected]>
Signed-off-by: Qingchuan Hao <[email protected]>
Signed-off-by: Qingchuan Hao <[email protected]>
Signed-off-by: Qingchuan Hao <[email protected]>
f327a41
to
bd8452e
Compare
Signed-off-by: Qingchuan Hao <[email protected]>
Signed-off-by: Qingchuan Hao <[email protected]>
…ed-storage-account
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Early feedback. Not yet finished reviewing.
Signed-off-by: Qingchuan Hao <[email protected]>
…ed-storage-account
eb502f1
to
9fd901a
Compare
Signed-off-by: Qingchuan Hao <[email protected]>
9fd901a
to
45392cb
Compare
Signed-off-by: Qingchuan Hao <[email protected]>
Signed-off-by: Qingchuan Hao <[email protected]>
Signed-off-by: Qingchuan Hao <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few comments but mostly looks good to me
deploy/legacy/manifests/controller/helm/retina/templates/operator.yaml
Outdated
Show resolved
Hide resolved
deploy/legacy/manifests/controller/helm/retina/templates/operator.yaml
Outdated
Show resolved
Hide resolved
LGTM on @rbtr 's feedback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks @mainred!
This PR introduces a managed storage account solution to Retina Capture, which managed the storage account resources on behalf the user under the azure resource group specified in the azure credential config file. After this, the user does not need to create even the secret and the captured network artificats will be uploaded to the storage account. If this pull request is related to any issue, please mention it here. Additionally, make sure that the issue is assigned to you before submitting this pull request. - [x] I have read the [contributing documentation](https://retina.sh/docs/contributing). - [x] I signed and signed-off the commits (`git commit -S -s ...`). See [this documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification) on signing commits. - [x] I have correctly attributed the author(s) of the code. - [x] I have tested the changes locally. - [x] I have followed the project's style guidelines. - [x] I have updated the documentation, if necessary. - [ ] I have added tests, if applicable. - After updating the helm charts - a storage account and a management policy rule to auto-delete blob after 7 days are created ![image](https://github.com/user-attachments/assets/fd93d954-8008-4b04-9afa-626463691405) - After applying a Capture - a blob container with retention policy is created ![image](https://github.com/user-attachments/assets/702dab18-b0a3-4468-830e-56a7449df889) - a k8s secret is created ![image](https://github.com/user-attachments/assets/834f8977-09e2-4cb6-a99a-578fec33cdb0) - network artifacts are uploaded the container after Capture duration ![image](https://github.com/user-attachments/assets/fa147554-8c93-48fe-99f4-65277391ea5b) - After deleting the capture - the secret is deleted ![image](https://github.com/user-attachments/assets/62c0fba4-7845-4792-8572-db412c704075) Add any additional notes or context about the pull request here. --- Please refer to the [CONTRIBUTING.md](../CONTRIBUTING.md) file for more information on how to contribute to this project. --------- Signed-off-by: Qingchuan Hao <[email protected]>
Description
This PR introduces a managed storage account solution to Retina Capture, which managed the storage account resources on behalf the user under the azure resource group specified in the azure credential config file.
After this, the user does not need to create even the secret and the captured network artificats will be uploaded to the storage account.
Related Issue
If this pull request is related to any issue, please mention it here. Additionally, make sure that the issue is assigned to you before submitting this pull request.
Checklist
git commit -S -s ...
). See this documentation on signing commits.Screenshots (if applicable) or Testing Completed
Additional Notes
Add any additional notes or context about the pull request here.
Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.