[Feature] Expose APIServer Service provisioned by karmada-operator

[RainbowMango]

Background
Currently, there is no reliable method to reference the Service for the Karmada APIServer. Users have to infer the Service based on internal implementation details, which can change over time, making this approach fragile and unreliable. This feature aims to provide a robust and stable way to expose Karmada services, particularly the APIServer, to external clusters or networks.

Proposal
#5599

The goal of this feature is to enhance the karmada-operator to include the Karmada API Server Service information in the status of Karmada resource objects. This will provide a standardized and reliable way for third-party applications to discover and interact with the Karmada API Server Service. The feature will ensure that the service information is consistently available and up-to-date, regardless of internal implementation changes.

Iteration Tasks

• Feature proposal. (@jabellard, Proposal: Add API Server Service Information to KarmadaStatus #5599)
• Restrict the supported ServiceType by adding some validations. (@RainbowMango, Restrict supported service types of Karamda APIServer supported by karmada-operator #5769)
• Enable Service type : LoadBalancer. (@chaosi-zju, enable LoadBalancer type karmada-apiserver service in operator #5773)
  • The runUploadAdminKubeconfig() didn't handle service with type LoadBalancer.
• Feature implementation
  • Code (@jabellard, Add API Server Service Information to KarmadaStatus #5775)
  • Test (@jabellard, Add API Server Service Information to KarmadaStatus #5775)
  • Documentation (@RainbowMango, Add docs for exposing Karmada APIServer provisioned by operator #6015)
    • We should have a doc to introduce how to access the karmada-apiserver, like Access The Argo CD API Server

[RainbowMango]

@jabellard @chaosi-zju What do you think of having a doc for this feature?
Let me know if you are going to help with it.

[jabellard]

@jabellard @chaosi-zju What do you think of having a doc for this feature? Let me know if you are going to help with it.

@RainbowMango , @chaosi-zju : Thanks for tackling the other items in this epic. I can do this last one. Today, we have some docs for the operator, so I'm thinking I can just add to it by adding instructions for discovering the API Server service for a Karmada instance. What do you think?

[RainbowMango]

Yes, I agree, users need the instructions for exporting APIServer.

For now, I think we can put the document at the operator README. For the long term, I guess we should move it to the website as we are going to have more documents.

[chaosi-zju]

so I'm thinking I can just add to it by adding instructions for discovering the API Server service for a Karmada instance.

Thanks your efffort, I can help reviewing your doc~

[RainbowMango]

@jabellard Any update?

[jabellard]

@jabellard Any update?

@RainbowMango , thanks for the reminder. I lost track of this umbrella issue at some point. Just submitted a PR for enhancing the docs.

[RainbowMango]

/close

[karmada-bot]

@RainbowMango: Closing this issue.

In response to this:

/close

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.