Skip to content

Commit

Permalink
feat(capture): add managed storage account support (microsoft#575)
Browse files Browse the repository at this point in the history
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]>
  • Loading branch information
mainred authored and ritwikranjan committed Aug 28, 2024
1 parent fbfdbd3 commit fb3d3eb
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/04-Captures/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,10 @@ See [Capture CRD](../05-Concepts/CRDs/Capture.md) for more details.

To simply the user experience, a managed storage account is configurable when setting up Retina, which can manage the storage account, container and Kubernetes secreting container the blob SAS on behalf the user. Check [managed-storage-account.md] for more details.

#### Managed Storage Account

To simply the user experience, a managed storage account is configurable when setting up Retina, which can manage the storage account, container and Kubernetes secreting container the blob SAS on behalf the user. Check [managed-storage-account.md] for more details.

#### Example

This example creates a Capture and stores the Capture artifacts into a storage account specified by Blob SAS URL.
Expand Down

0 comments on commit fb3d3eb

Please sign in to comment.