-
Notifications
You must be signed in to change notification settings - Fork 858
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
Unexplained "dryRun is not supported" error for deploying Application targetted at OCM cluster #5361
Comments
Could you see what cluster-gateway image version are you using? You could run |
v1.7.0-alpha.3 |
I guess it might be because the OCM cluster proxy does not support the dryrun request proxy. Could you try to add |
We're still getting that error with Vela 1.9.9 Our cluster gateway is 1.9.0-alpha2. @Somefive Any idea where to look to understand/fix this issue? Thanks |
We saw that Cluster Gateway 1.9.0 was released, but that does not solve the issue. Would any of the Kubela maintainers ( @FogDong ? @wonderflow ? @Somefive ?) please give a clue on how to solve this issue. Thanks guys, |
Hi, have you tried adding |
Hey @FogDong yes that works although we'd like to keep the pre-dispatch dry run if possible. Are you telling me it's not compatible with multicluster deployment? |
Yeah I think right now OCM cluster proxy still does not support the dryrun request proxy. Any insights from @Somefive ? |
@FogDong to clarify we're not using OCM ManagedCluster, just regular cluster join. Is it still expected that dryRun does not work? |
In a standard cluster setup, the |
@FogDong it's not working correctly for us. We use normal We have to disable dry runs unfortunately. Any clues on what could be the problem here? |
Bump, any idea @FogDong? Thanks in advance |
Describe the bug
Application workflow fails with "cannot create object: dryRun is not supported)" with OCM managedclusters
To Reproduce
Expected behavior
Should detect cluster and deploy application
KubeVela Version
CLI Version: v1.7.0
Core Version: 1.7.0
Cluster information
1.24.0
The text was updated successfully, but these errors were encountered: