Azure / Azure/vscode-aks-tools
Enhancement and Quality: Retina x Enable Auto Storage account detection and uploading logs directly into those storage accounts.
- Dominant language
- TypeScript
- Stars
- 65
- Forks
- 78
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 22
Description
### Enhancement details:
One of the offering Retina provides is, uploading the node distributed captures into the storage account:
* https://retina.sh/docs/captures/cli#examples-1
Store the capture file to a storage account
```
kubectl retina capture create --blob-upload --node-selectors "kubernetes.io/os=linux"
```
### How:
We could easily enable this in more ATOMIC way, and here is how: (Simple first behaviour could be as follows)
* **Diagnostic settings** in AKS settings has a setting to hold the default storage account or to hook storage account.
* If, cluster has `diagnostic setting` we present user which account they want to choose,
* Upon, `selecting` the storage account, we then let user select which nodes they want this tool to run,
* In the end, we then run the above distributed nature run for the `blobstorage` account to have all updated.
### Pros
This provide more organic way for the user to have those logs available to the user and user could either generate the temporary access for support access for those logs or download according to their needs.
Contributor guide
Research direction
Read the Retina capture CLI examples, especially the `kubectl retina capture create --blob-upload` flow, alongside AKS diagnostic settings. Define the storage-account selection and node-selection workflow, then verify that completion runs the distributed capture upload and makes the logs available in the selected account.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100