move registration feature gates to api, can be used by registration-o…

[ivan-cai]

move registration feature gates to api, can be used by registration-operator for check input feature gates if valid.

Signed-off-by: ivan-cai caijing.cai@alibaba-inc.com

[ivan-cai]

@qiujian16 As we discussed in registration-operator pr 230

[qiujian16]

hrm, could we just define the feature name or feature spec in api? I do not think we should have init here, this could be messy when others import api given feature is a global var.

[ivan-cai]

hrm, could we just define the feature name or feature spec in api? I do not think we should have init here, this could be messy when others import api given feature is a global var.

@qiujian16 I have delete init() and DefaultSpokeMutableFeatureGate & DefaultHubMutableFeatureGate. Plz review again.

[qiujian16]

thanks, one more nit thing. How about we have a separate package like feature to put it? I do not think it relates to a certain version of API, right?

[ivan-cai]

thanks, one more nit thing. How about we have a separate package like feature to put it? I do not think it relates to a certain version of API, right?

@qiujian16 Yes, I have changed. Plz review again, thanks!

[qiujian16]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ivan-cai, qiujian16

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:

• OWNERS [qiujian16]

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