Perms update

[allisoneer]

Important

Increase memory limits, update image tag, and expand RBAC permissions in Kubernetes configuration.

• Resource Limits:
  • Increase memory limit from 512Mi to 2048Mi in manager.yaml for the controller.
• Image Update:
  • Update controller image tag to 202505141822 in kustomization.yaml.
• RBAC Permissions:
  • Add watch verb for namespaces in namespace_permissions_patch.yaml.
  • Add full CRUD and watch permissions for secrets and events in namespace_permissions_patch.yaml.

^{This description was created by for a10f26f. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to a10f26f in 1 minute and 9 seconds. Click for details.

• Reviewed 60 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 4 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. acp/config/localdev/kustomization.yaml:29

• Draft comment:
  Updated controller image tag to '202505141822'. Verify the new tag aligns with the intended build release.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. acp/config/manager/manager.yaml:93

• Draft comment:
  Memory limit increased from 512Mi to 2048Mi. Ensure this change matches the application's resource needs and cluster capacity.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. acp/config/rbac/namespace_permissions_patch.yaml:15

• Draft comment:
  Added 'watch' verb to namespaces rule. Confirm that this additional permission is necessary.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. acp/config/rbac/namespace_permissions_patch.yaml:16

• Draft comment:
  New RBAC rules for secrets and events have been added. Ensure these permissions follow the least privilege principle to avoid over-privileging.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to ensure that the new RBAC rules follow the least privilege principle. This falls under the category of asking the author to double-check or ensure something, which is against the rules.

Workflow ID: wflow_rjplSlqPRY4pEvna

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}