Epic Goal

Auto import is triggered by creating an auto-import-secret that contains the kubeconfig or server+token and
autoImportRetry count. Once started, the controller deletes the secret, so there is no way to know that auto-import is being attempted. We need conditions on the ManagedCluster or some way that the UI can tell: * That auto import is being attempted

• What the autoImportRetry count is, and the number of the current attempt
• If the retry attempt limit has been reached and cluster has failed to import

ACM backlog issue:  https://github.com/open-cluster-management/backlog/issues/14311 

Why is this important?

• The user should be able to be notified when an action taken is unsucessful
• The UI needs a way to inform the user that the import action failed
• The UI should not provide the manual import command when auto import is being used

Scenarios

1. API supports condition that indicates an auto-import process is in progress
2. API supports a condition that indicates an auto-import process has failed
3. API supports a condition that indicates an auto-import process has succeeded
4. API supports a configurable retry count, and indicates the current retry attempt
5. Auto import secret is not deleted until all retry attempts have completed

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

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 - Downstream documentation merged: <link to meaningful PR>

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• _ FIPS Readiness
• _ Works in Disconnected
• _ Global Proxy Support
• _ Installable to Infrastructure Nodes
• _ No impacts to Performance and Scalability
• _ Backup and Restorable