Fix:search http response add content-type header

[callmeoldprince]

What type of PR is this?
/kind bug

What this PR does / why we need it:
Adding HTTP response headers for k8s native clients to decode normally
Which issue(s) this PR fixes:
Fixes:Search service request returns text/plain by default

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

`karmada-search`: Fixed contecnt-type header issue in HTTP response.

[XiShanYongYe-Chang]

Hi @callmeoldpince, thanks for your feedback. Can you explain why it's set up to application/json by default? Will there be other format requirements? Do we need to add a new parameter to control this parameter?

[jwcesign]

I tried with kube-apiserver, the header is Content-Type: application/json.

I think the benefit is: make some json parse tools work fine. cc @callmeoldpince Do I understand correctly?

[callmeoldprince]

Hi @callmeoldpince, thanks for your feedback. Can you explain why it's set up to application/json by default? Will there be other format requirements? Do we need to add a new parameter to control this parameter?

I tried with kube-apiserver, the header is Content-Type: application/json.

I think the benefit is: make some json parse tools work fine. cc @callmeoldpince Do I understand correctly?

@jwcesign @XiShanYongYe-Chang
i use "sigs.k8s.io/controller-runtime/pkg/client/typed_client.go” link search-server,and call client Get(ctx context.Context, key ObjectKey, obj Object) error or List(ctx context.Context, list ObjectList, opts ...ListOption) func,If not set content-type,default value is text/plain; charset=utf-8, for sigs.k8s.io/controller-runtime/pkg/client,failure serializer for text/plain; charset=utf-8.
In summary, the sigs.k8s.io/controller-runtime/pkg/client is not implemented for type text/plain; charset=utf-8

[jwcesign]

@callmeoldpince I think this is not a bug.
cc @RainbowMango , do we need to cherry-pick this?

[RainbowMango]

cc @RainbowMango , do we need to cherry-pick this?

Both are OK with me.

@callmeoldpince are you using Karmada in production? Do you need this patch on release branches?

[RainbowMango]

cc @RainbowMango , do we need to cherry-pick this?

Both are OK with me.

@callmeoldpince are you using Karmada in production? Do you need this patch on release branches?

[callmeoldprince]

cc @RainbowMango , do we need to cherry-pick this?

Both are OK with me.

@callmeoldpince are you using Karmada in production? Do you need this patch on release branches?

yes,I hope it can be merged into release1.5

[XiShanYongYe-Chang]

Thanks~ @callmeoldpince, I think we can do it. Can you help add a release-note here:

so that we can describe it in cherry-pick.

[jwcesign]

/lgtm

Hi @callmeoldpince Can you help cherry-pick this PR to branch release-1.5/release-1.4?

[callmeoldprince]

Thanks~ @callmeoldpince, I think we can do it. Can you help add a release-note here:

so that we can describe it in cherry-pick.
done

[XiShanYongYe-Chang]

Sorry, I didn't describe it clearly. Can you change it to something like this?

karmada-search: http response add content-type header

[callmeoldprince]

/lgtm

Hi @callmeoldpince Can you help cherry-pick this PR to branch release-1.5/release-1.4?

I hope it can be merged into release1.5

[callmeoldprince]

Sorry, I didn't describe it clearly. Can you change it to something like this?

karmada-search: http response add content-type header

done

[XiShanYongYe-Chang]

I hope it can be merged into release1.5

We can sync it to all the versions we've affected before.

[XiShanYongYe-Chang]

Ask @RainbowMango to help run the ci test.
/cc @RainbowMango

[RainbowMango]

Done.

[XiShanYongYe-Chang]

/approve
Thanks~

Hi @callmeoldpince excuse me, would it be convenient to reveal the name of your company?

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: XiShanYongYe-Chang

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

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/registry/OWNERS [XiShanYongYe-Chang]

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

[XiShanYongYe-Chang]

Hi @callmeoldpince, thanks a lot.

This patch have been merged, would you like to help cherry-pick it to the previous branch: release-1.3, release-1.4, release-1.5. You can cherry-pick refer to: https://karmada.io/docs/next/contributor/cherry-picks/

[callmeoldprince]

Hi @callmeoldpince, thanks a lot.

This patch have been merged, would you like to help cherry-pick it to the previous branch: release-1.3, release-1.4, release-1.5. You can cherry-pick refer to: https://karmada.io/docs/next/contributor/cherry-picks/

@XiShanYongYe-Chang I refer to the document to operate

[XiShanYongYe-Chang]

@XiShanYongYe-Chang I refer to the document to operate

Thanks~, please help update the release note in the new pr.

[callmeoldprince]

@XiShanYongYe-Chang I refer to the document to operate

Thanks~, please help update the release note in the new pr.

ok,done

[RainbowMango]

Thanks @callmeoldpince and welcome to Karmada community~