[enhancement] Should not use Float in CRD definition.

[gaocegege]

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Ref kubernetes-sigs/controller-tools#245

so, it's technically supported, but floats are highly discouraged (and disallowed in official kubernetes APIs) because they won't round-trip properly, can't actually represent certain numbers exactly, etc (all the normal reasons floats are usually not what you want in a program). We recommend using resource.Quantity or int32 for your numeric types, in accordance with the Kubernetes API conventions.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

[gaocegege]

/priority p3

[gaocegege]

We can use https://golang.org/src/encoding/json/decode.go#L187 json.Number.

[issue-label-bot]

Issue Label Bot is not confident enough to auto-label this issue.
See dashboard for more details.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
area/front-end	0.83

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[andreyvelich]

@gaocegege Is it better than just a simple string, like we did with metrics values ?

[gaocegege]

json.Number is a wrapper of string. We can use string, too.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[andreyvelich]

/lifecycle frozen