RATIVERA
Trust begins with clear boundaries.
Review what the AKS assessment reads, which access you grant, and where your team retains control.
No RATIVERA agent in your AKS cluster.
The AKS path uses authorized Azure resource configuration and monitoring data. This does not mean your cluster needs no monitoring components: Azure Managed Prometheus and the required retained series must already be available.
Two roles. Separate scopes.
Discovery Reader
Subscription-scoped reads identify AKS clusters and their monitoring configuration. This role does not grant the evidence-query permissions.
Evidence Reader
Assigned to a specific enrolled AKS resource to read cluster and node-pool facts and query resource-scoped metrics.
A decision does not apply a change.
Azure assessment access is read-only. Git permissions are a separate authorization. Accepting a recommendation records your decision; your team reviews and deploys changes through its own process.
Do not assume Microsoft-managed workloads are protected by an enforced exclusion. Their treatment must be confirmed for the deployed environment.
Data-handling questions deserve specific answers.
The assessment uses resource configuration, CPU and memory telemetry, and workload context. Detailed stored-field inventory, hosting and processing locations, retention, deletion, and contractual terms remain launch review items. This page makes no certification or compliance claim.
Before granting access, request the current access and data-handling information for your evaluation.
You can withdraw Azure access.
Have an authorized Azure administrator remove the relevant role assignments. Discovery and evidence access are independently revocable; removing discovery alone does not stop evidence acquisition for an already connected cluster.
One Problem at a Time · Episode 4 · 1:07
Why shouldn't optimization tools change production automatically?
Acceptance records intent; your team reviews, merges, and deploys through its own change process.
The decision panel is from a local test cluster, not AKS. The opening failure is an illustrative scenario. Git steps describe the customer’s workflow; the episode does not demonstrate RATIVERA creating, merging, or executing a pull request.
English captions are burned into the video. An optional English caption track and transcript are also available. Use fullscreen for small screen details.