Skip to content

Conversation

@macayaven
Copy link

Add detailed documentation for the ACM (Advanced Cluster Management) cluster provider feature, including:

  • Overview and architecture of ACM multi-cluster support
  • Configuration guide for both acm-kubeconfig and acm strategies
  • Step-by-step setup instructions with examples
  • Prerequisites and RBAC requirements
  • Troubleshooting guide for common issues
  • Security considerations and best practices
  • Production deployment examples

This documentation complements the ACM cluster provider implementation merged in PR #58.

🤖 Generated with Claude Code

Add detailed documentation for the ACM (Advanced Cluster Management)
cluster provider feature, including:

- Overview and architecture of ACM multi-cluster support
- Configuration guide for both acm-kubeconfig and acm strategies
- Step-by-step setup instructions with examples
- Prerequisites and RBAC requirements
- Troubleshooting guide for common issues
- Security considerations and best practices
- Production deployment examples

This documentation complements the ACM cluster provider implementation
merged in PR openshift#58.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@openshift-ci openshift-ci bot requested review from ardaguclu and matzew October 30, 2025 21:21
@openshift-ci
Copy link

openshift-ci bot commented Oct 30, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: macayaven
Once this PR has been reviewed and has the lgtm label, please assign cali0707 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 30, 2025
@openshift-ci
Copy link

openshift-ci bot commented Oct 30, 2025

Hi @macayaven. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@macayaven
Copy link
Author

Closing in favor of #66 which has a clean commit history and follows Red Hat PR requirements.

@macayaven macayaven closed this Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant