You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
@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?
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.
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
KarmadaStatus
#5599)LoadBalancer
. (@chaosi-zju, enable LoadBalancer type karmada-apiserver service in operator #5773)LoadBalancer
.KarmadaStatus
#5775)KarmadaStatus
#5775)The text was updated successfully, but these errors were encountered: