Scenario 3 - Defense Updates
Open
- Dominant language
- Shell
- Stars
- 10
- Forks
- 14
- Avg merge
- 10d 18h
- Merged PRs (30d)
- 1
Description
- after detection of malicious container, we could delete the cluster and redeploy / re-attach to the existing ACR.
- defender for containers
- ACR permissions restrictions
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or an entry point. Clarify whether Scenario 3 should cover deleting and redeploying the cluster, re-attaching to the existing ACR, Defender for Containers, or ACR permission restrictions, and define what completion looks like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes
- Domain
- cloud, devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100