Skip to content

Comments

Configure ingress-authz-overlay to use centralized authz-adapter#97

Merged
bwalsh merged 2 commits intofeature/ingressfrom
copilot/sub-pr-92-again
Nov 25, 2025
Merged

Configure ingress-authz-overlay to use centralized authz-adapter#97
bwalsh merged 2 commits intofeature/ingressfrom
copilot/sub-pr-92-again

Conversation

Copy link
Contributor

Copilot AI commented Nov 25, 2025

Two authz-adapter instances were running: one in security namespace (from main argo-stack chart) and one in argo-stack namespace (from ingress-authz-overlay). The overlay should reuse the centralized adapter, not deploy its own.

Changes

  • values.yaml: Set deploy: false and namespace: security to point to existing adapter
  • Documentation: Updated README.md and user guide to explain centralized vs. standalone configuration

Configuration

ingressAuthzOverlay:
  authzAdapter:
    deploy: false          # Don't deploy separate instance
    namespace: security    # Point to centralized adapter
    serviceName: authz-adapter
    port: 8080

Ingress annotations now route auth checks to http://authz-adapter.security.svc.cluster.local:8080/check.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: bwalsh <47808+bwalsh@users.noreply.github.com>
Copilot AI changed the title [WIP] Add authz-aware ingress overlay for multi-tenant UIs and APIs Configure ingress-authz-overlay to use centralized authz-adapter Nov 25, 2025
Copilot AI requested a review from bwalsh November 25, 2025 06:04
@bwalsh bwalsh marked this pull request as ready for review November 25, 2025 06:05
@bwalsh bwalsh merged commit 0a59706 into feature/ingress Nov 25, 2025
@bwalsh bwalsh deleted the copilot/sub-pr-92-again branch November 25, 2025 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants