You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now I am using cluster-proxy v0.3.0 and it seems that cluster-proxy doesn't return any value in AddOnConfiguration.CRName for clustermanagementaddons because probably addOnConfiguration is deprecated.
$ kubectl get clustermanagementaddons
NAME DISPLAY NAME CRD NAME
cluster-proxy cluster-proxy
Hi, @mikeshng it's a clusteradm issue, as @yana1205 mentioned above, it's because clusteradm is using a deprecated field to Get the managedproxyconfiguration. That's exactly the root cause, thanks for reporting @yana1205
Hi, I am going through https://open-cluster-management.io/getting-started/integration/cluster-proxy/ and facing the following error at the step of "Command-line tools" in "Usage" section.
Probably this issue is relating with this comment (https://github.com/open-cluster-management-io/clusteradm/blob/main/pkg/cmd/proxy/health/exec.go#L106) so will be fixed sooner or later but let me open it.
Now I am using cluster-proxy v0.3.0 and it seems that cluster-proxy doesn't return any value in
AddOnConfiguration.CRName
for clustermanagementaddons because probablyaddOnConfiguration
is deprecated.If I switch to use
supportedConfigs[0].defaultConfig.name
field (the value is actuallycluster-proxy
) at https://github.com/open-cluster-management-io/clusteradm/blob/main/pkg/cmd/proxy/health/exec.go#L109 as the comment indicates, it turns into working.Environment
clusteradm
cluster-proxy addon: v0.3.0
managed-serviceaccount addon: v0.3.0
The text was updated successfully, but these errors were encountered: