-
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
ClusterResourceSet feature does not work #4878
Comments
The errors seem to hint to a network issue, which isn't necessarily related to ClusterResourceSet |
/milestone Next |
suggests DNS resolution failure. |
Thanks @randomvariable and @vincepri , let me retest. @wangjsty ^^ |
Closing this due to lack of updates, please feel free to reopen if you have more details /close |
@vincepri: Closing this issue. 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. |
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
Please refer to kubernetes-retired/cluster-api-provider-nested#155 for detail.
Follow the proposal guides:
The following problem appears, but the two apiservers are running normally by kubectl command.
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: