Epic Goal

...

we need to review and gaps and ensure the following below is covered:

1. Advanced Customization (so that configuration-policy is used)

Here are the major settings to be adjusted

• resource limit and request for each argocd component (application controller, redis, and repo server)
  resourceCustomizations. This is for specifying custom health check, actions, ignore differences for specific kind resource. e.g. the following section define a custom health check for argocd application. When there is argocd application created/updated. the custom health check is used instead of the default health check.

argoproj.io/Application:
  health.lua: |
    <Lua script for custom health assessment>
  actions.lua: |
    <Lua script for custom actions>

*

  ignoreDifferences: |resourceExclusions  

This is to specify which kinds of resources are excluded from the ArgoCD sync progress.
We can enhance our gitops addon for customizing these 3 sections in ArgoCD kind resource. Users can define their own sections through ACM addonDeploymentConfig.

2. The second usecase is to support different namespaces and instances. See scenarios and see Applications in any namespace

Why is this important?

...

Scenarios

...
user1 creates appset1 in ns1 on the hub cluster
user2 creates appset2 in ns2 on the hub cluster
each user can only see the appset created in their own namespace
each app could be propagated to different ns on the same managed cluster.
Enabling any namespace for app has been implemented in our new gitops addon. We can verify the use case using ArgoCD pull model with our new gitops addon

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)