Define and unify Flux controller standards

[scottrigby]

There are several problems which will be solved by defining and unifying Flux controller standards.

Work on this is well underway. This meta issue is to form specific issues and tasks into a coherent multi-step plan, so that team members can both collaborate and work in parallel to make this effort as efficient and successful as possible.

Linked issues:

• [x] Stage 0: https://github.com/fluxcd/pkg/issues/117
  • [x] https://github.com/fluxcd/pkg/pull/125
• [ ] Stage 1: https://github.com/fluxcd/flux2/issues/1601
• [ ] Stage 2: https://github.com/fluxcd/website/issues/398
• [ ] Stage 3: https://github.com/fluxcd/website/issues/400

[pjbgf]

The unified standards are defined, but still being improved as they are rolled out across the controllers. Temporary reference can be found at:

• Controller Patterns
• kstatus conditions
• kstatus - conditions and generations check

[stefanprodan]

I'm closing this umbrella issue for the same reason mentioned here: https://github.com/fluxcd/flux2/issues/1601#issuecomment-1603092405