[Feature]: Operator can install Korifi without needing HNC

[julian-hj]

Blockers/Dependencies

No response

Background

As an Operator I want fewer dependencies So that I can more easily run Korifi

Acceptance Criteria

GIVEN I have docker and kind installed WHEN I use the deploy-on-kind.sh script THEN I see that HNC no longer gets installed AND I can still use the product to create orgs and spaces and cf push

Dev Notes

• A separate story will cover the updates to installation instructions.

• 769 covers the spike work we did to try this out. That work did not include watching existing roles, rolebindings, and secrets to propagate changes. It also didn't include the finalizer we will need to delete namespaces when a CFOrg or CFSpace gets deleted.

• Proposed implementation is covered in more detail in this proposal document
• Consider switching Eirini namespaced roles to a ClusterRole so that we don't have to propagate them. We will still need the rolebinding to be created in new namespaces, but shouldn't need to watch for updates.
• We will need to watch the root namespace for the appearance of new RoleBindings

[clintyoshimura]

Changes that need to be done:

• Orgs
  • [x] Propagation of resources at creation time
  • [x] Propagation of added/changed/deleted resources
  • [x] Finalizer deletion of managed namespaces
• Spaces
  • [x] Propagation of resources at creation time
  • [x] Propagation of added/changed/deleted resources
  • [x] Finalizer deletion of managed namespaces
  • [x] remove installing HNC from deploy-on-kind script
  • [x] Remove code that waits for HNC in API
  • [x] Remove code that waits for HNC in tests

[clintyoshimura]

In order to switch the eirini roles to ClusterRoles we may need to make changes to eirini-controller. That might be more appropriate to do as a separate story.

[julian-hj]

A/C passed