Unifying NFD operator and operand repositories

[yevgeny-shnaidman]

What would you like to be added:
Currently NFD operator code and NFD operand code are residing in 2 different independent repositories. We can unify those repositories into one repository that will include both operator and operand code and deployments. It will also means that any PR to the unified repository will be verified via operator deployment and execution.

Why is this needed:

1. Having 2 different repos requires synchronization for major commits between operand and operator, in order to support new features in the operator.
2. Currently some of the APIs are defined and reside in the operand repository, which requires synchronizing them into the operator repository and adding their deployment to the operator code.
3. Since most of the development is done on the operand code, the operator code is neglected, and frequently becomes broke due to reasons 1 and 2
4. Unifying repos will remove the duplication of the APIs mention in 2.
5. We can still support deployment of operand alone, if this will be required by the users.
6. Unifying will allow easier deployment of the NFD via operator, which is more conventional K8s way
7. Unifying repos will allow unified release for both operator and operand
8. It will also allow easier upgrade process, since the operand image will be more accessible to the operator

[yevgeny-shnaidman]

/cc @marquiz @ArangoGutierrez

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale