-
Notifications
You must be signed in to change notification settings - Fork 308
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
Hypershift does not support non-default CNI on the Hosted Cluster #3927
Comments
@sujeet-kr you may want to update your hypershift CLI. It looks like you are using a very old version. Try using one you build from |
Thank you for your response @csrwng . The above issue was experienced with the cli built from main. I used the steps from https://hypershift-docs.netlify.app/getting-started/ |
|
Here is the yaml -
|
Don't think this would be useful but here is the version of Hypershift I built and used - |
@sujeet-kr can you include the version of the hypershift operator on the cluster? (should be first line in log) |
Had to recreate the management cluster. Here is the log with the version -
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
I tried provisioning a Hosted cluster with Hypershift on AWS using
--network-type
toOther
using,The command did not error out and the nodes for the hosted cluster got created, but on checking
kubectl get --namespace clusters hostedclusters
noticed the error -ValidConfiguration condition is false: service type OVNSbDb not found
for the hosted cluster.Also tried creating the Hosted Cluster using the yaml spec and setting
HostedCluster.spec.networking.networkType
toOther
got the same error as with the cli.Hosting cluster OCP version - 4.15.4
Hosted cluster tried - 4.15.9
The text was updated successfully, but these errors were encountered: