Somefive

> When reading the **code implementation** part of **title generation**, I found that the decoding strategy generation method is **different** of FOS. It is more like the method of **Prefix...

Could you see what cluster-gateway image version are you using? You could run `kubectl get deployment -n vela-system -owide` and see it.

I guess it might be because the OCM cluster proxy does not support the dryrun request proxy. Could you try to add `--set featureGates.preDispatchDryRun=false` to the `helm install` process. It...

Could you try to delete the KubeVela core controller's pod and restart it and try?

It seems your OCM cluster is okay for cluster-gateway to connect. And your application reports "cluster ocp-cluster cannot be found"?

In deployment.yaml, we set the image field to `"{{ .Values.image.repository }}:{{ .Chart.AppVersion }}"` which reuse field AppVersion (appVersion) in Chart.yaml. You can add `image.tag` field in values.yaml and set image...

> ping @FogDong , does it mean CUE don't support generate OpenAPI json schema in this case? Maybe we need to report it to the CUE community. I have confirmed...

Thanks for the contribution! 1. It seems that you mainly change https://github.com/kubevela/kubevela/blob/2f7b8b5ba898d914b812e93ba6be56dbf1dd2776/vela-templates/definitions/internal/workflowstep/collect-service-endpoints.cue#L74 if I'm understanding it correctly? If so, I would recommend directly add `endpoints` there and do not need...

> I see. Seems the problem is that go lint takes some time. In your case, you can try run `make manifests fmt vet staticcheck`. This should skip lint.

> > > > > > > > > I see. Seems the problem is that go lint takes some time. In your case, you can try run `make manifests...