Skip to content

https://issues.redhat.com/browse/ACM-20220 Access apiserver token doc #7951

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 13 commits into
base: 2.14_stage
Choose a base branch
from

Conversation

oafischer
Copy link
Contributor

2.14 only.

Checklist considered.

@oafischer oafischer requested review from xuezhaojun and dtthuynh June 12, 2025 09:10
@@ -40,6 +40,7 @@ Learn about new features and enhancements that come with the {mce-short} install
Learn about new features and enhancements for Cluster lifecycle with {mce-short}.

- You can now define a unique mirror registry for each cluster. To learn more, see xref:../assisted_installer#config-mirror-reg-cluster[Configuring mirror registries for each cluster]
- You can now access the managed cluster `kube-apiserver` by using a hub cluster user token. To learn more, see xref:../cluster_proxy_addon_use#access-kube-apiserver-hub-token[Accessing the managed cluster `kube-apiserver` by using a hub cluster user token].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be "a managed cluster's kube-apiserver" as it points to some target managed cluster?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, "managed cluster's kube-apiserver" would be more accurate.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't use a possessive as per the style guide in this case. What we have in the PR would match the style requirements, but if it's not accurate enough, would "kube-apiserver of the managed cluster" be better/more accurate?

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oafischer Agree!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oafischer oafischer requested a review from dtthuynh June 13, 2025 09:30
@xuezhaojun
Copy link
Contributor

/lgtm

@oafischer
Copy link
Contributor Author

oafischer commented Jun 18, 2025

All comments addressed, merging after peer review

Copy link
Collaborator

@amolnar-rh amolnar-rh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! I only have a few nits. PTAL and let me know when you want me to re-review.

[#use-cluster-proxy-addon]
= Using cluster proxy add-ons

Use cluster proxy add-ons to access the managed cluster kube API server or managed cluster services by using different methods. See the following topics to learn more about the different ways you can use cluster proxy add-ons.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a link to the topics. I understand that these topics are in the rest of the section but I'm expecting to see the relevant topics listed right after this intro sentence ("See the following topics..."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated


See the following example that binds the `get` and `list` permissions for pods to the user `developer`:

[source,yaml]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't you need a + here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's only needed when it comes after a step (.)

@oafischer oafischer requested a review from amolnar-rh June 18, 2025 12:49
@openshift-ci openshift-ci bot added the lgtm label Jun 18, 2025
Copy link

openshift-ci bot commented Jun 18, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amolnar-rh, oafischer, xuezhaojun

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-merge-robot
Copy link

PR needs rebase.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants