remove go.mod dependency on k8s.io/kubernetes

[medyagh]

currently in our go.mod we are depending on

k8s.io/kubernetes v1.21.2

which is not a good idea to use the whole kubernetes project as a lib, we currently only use a few "Constants" and feature gate types (to validate if a feature gate is valid)

I would suggest we copy those constants from kubernetes source code to our own constants file in constants package maybe k8s_constants.go

we cna update once a while manually using make target, to copy/update those constants from k8s source code.

make update-constants

and then remove the dependency to k8s.io/kubernetes in our go mod

[mahalrs]

I will work on this.

/assign @mahalrs

[medyagh]

cool its yours @mahalrs

[mahalrs]

@medyagh
Should we copy all constants or only the ones that we are using? Also, what are we going to do with feature gate types. Currently we are only using keys from InitFeatureGates map. So, we can copy the keys from the map and store them in a slice. Also should we put this slice in pkg/constants/k8s_constants.go or something like pkg/constants/k8s_features.go.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale