kustomize build with diable unique keys

[xyz-li]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The official version of kustomize returns errors when yaml contains duplicated keys. The reason is the upgrading package of go-yaml/yaml. I have had opened a pr to address this problem, but there was no response from the go-yaml maintainer. By the way, the last commit of go-yaml/yaml is at 2021-01-08, which is about eight months ago. Then I opened a pr to kubernetes-sigs/kustomize, the maintainer would wait to see what the go-yaml maintainer says. So I have to fork the repo kubernetes-sigs/kustomize, and add options to disable the unique keys. If the pr is closed, we will use the official version of kustomize.

https://github.com/kubesphere/kustomize/pull/1

Which issue(s) this PR fixes:

Fixes #3933

Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

[zryfish]

That's a big change, I think we'd better fix it from upstream. Since there is a PR opened to go-yaml, maybe we can find a way to reach to go-yaml maintainers.

[ks-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: xyz-li
To complete the pull request process, please assign wansir after the PR has been reviewed.
You can assign the PR to them by writing /assign @wansir in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

Merging #4114 (9f385d0) into master (fa4c899) will decrease coverage by 1.58%.
The diff coverage is n/a.

❗ Current head 9f385d0 differs from pull request most recent head f0b2ab6. Consider uploading reports for the commit f0b2ab6 to get more accurate results

@@            Coverage Diff             @@
##           master    #4114      +/-   ##
==========================================
- Coverage   28.11%   26.53%   -1.59%     
==========================================
  Files         217      217              
  Lines       22152    23448    +1296     
==========================================
- Hits         6228     6221       -7     
- Misses      14895    16180    +1285     
- Partials     1029     1047      +18     

Flag	Coverage Δ
unittests	26.53% <ø> (-1.59%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...mple/client/openpitrix/helmwrapper/helm_wrapper.go	23.29% <ø> (ø)
...ller/destinationrule/destinationrule_controller.go	36.81% <0.00%> (-10.00%)	⬇️
...controller/groupbinding/groupbinding_controller.go	62.67% <0.00%> (-2.12%)	⬇️
...g/controller/application/application_controller.go	65.51% <0.00%> (-2.07%)	⬇️
...controller/notification/notification_controller.go	52.08% <0.00%> (-0.61%)	⬇️
pkg/apiserver/config/config.go	55.55% <0.00%> (-0.41%)	⬇️
pkg/models/resources/v1alpha3/resource/resource.go	85.29% <0.00%> (-0.22%)	⬇️
pkg/models/openpitrix/utils.go	35.09% <0.00%> (-0.14%)	⬇️
pkg/models/monitoring/monitoring.go	0.00% <0.00%> (ø)
pkg/kapis/resources/v1alpha3/register.go	0.00% <0.00%> (ø)
... and 36 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fa4c899...f0b2ab6. Read the comment docs.

[xyz-li]

That's a big change, I think we'd better fix it from upstream. Since there is a PR opened to go-yaml, maybe we can find a way to reach to go-yaml maintainers.

I have sent message to the maintainer on twitter. Waiting for his response.

[xyz-li]

/hold