-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update Doc for Managed k8s service #7032
Comments
@pydctw: The label(s) In response to this:
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/test-infra repository. |
/kind documentation |
/help |
@fabriziopandini: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
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/test-infra repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
Unfortunately this issue isn't gaining traction, but keeping it around because improvement to the documentation will be more than welcome /triage accepted |
User Story
As a Cluster API provider developer, I would like to have a doc describing clear contracts between CAPI and providers for managed k8s service.
Detailed Description
When Managed Kubernetes in CAPI proposal is approved, CAPI doc should be updated to reflect the chosen API option.
This is not an exhaustive list and feel free to add items in the comments.
controlPlaneEndpoint
in the scenario where the control plane creates the api server load balancer. We should include sample code.InfrastructureReady
is true.The text was updated successfully, but these errors were encountered: