Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In upstream upgrade PR, open-cluster-management-io/cluster-proxy#207, it upgrade to using latest image in clusteradm as well.
But in downstream, we don' have this field updated.
@qiujian16 From the question in channel: https://kubernetes.slack.com/archives/C01GE7YSUUF/p1729251075877059. cluster-proxy-addon is not widely used in the community.
So I want to propose to archive cluster-proxy in ocm-io step by step, and then merge cluster-proxy-addon and cluster-proxy repo in stolostron. This way, we can save our energy on diff management and e2e fails on this component.
--
Kudo to @haoqing0110 , help quickly debug the e2e failure.