* add data science migration to init

Co-authored-by: Bartosz Majsak <[email protected]>

* chore: removes unused test setup

* feat(test): sets up testing for ossm plugin

* feat(make): adds test-ossm target

* feat: introduces OssmResourceTracker resource

It is a cluster-scoped resource for tracking objects created by Ossm plugin.
Primarily used as owner reference for resources created across namespaces
so that they can be garbage collected by Kubernetes when they are not needed anymore.

* feat: uses OssmResourceTracker to cleanup owned resources

- adds cleanup hook for Delete phase of KfDef operator
- moves k8s_utils code to ossm package to keep it in one place for future extraction of the logic

* chore: renames plugin to OssmInstaller

* chore: moves cleanup logic to single file

* feat: handles token volume removal in SMCP

* chore: adds plugin name as extra key-value to logger

* feat: removes extAuthzProvider on deletion

* chore: minor naming fixes

embed templates to OSSM plugin

Co-authored-by: Bartosz Majsak <[email protected]>

they might have been removed in some merge (?)

* add prereq checks to init, add tests
---------

Co-authored-by: Bartosz Majsak <[email protected]>

- easy builder to define what particular feature consists of
- enables the use of existing YAML manifests
- allows the definition of additional resources programmatically with a simple func registration
- cleanup functions are now part of each feature and are called one after the other
- each feature has its own resource tracker object
- ability to test smaller parts of the whole thing by using `Feature`s in integration tests

* chore: extracts smcp GVR to a var

and reuse it in smcp-related funcs

* fix: returns err on oauth creation failure

instead of nil by mistake

* feat: adds ability to enable feature based on predicates

in certain cases this information can only be determined at runtime, for example based on user-defined values of the plugin spec.

* feat: introduces control plane installation

coupled with wait condition

* fix: makes feature enabled by default

* chore: reworks smcp creation

It relies on owner reference so can be cleaned up as other resources

* fix: applies cleanups only if feature is enabled

Additionally moves OssmResourceTracker creation to .Apply func

* feat: reworks plugin integration to use Apply and Delete funcs of KfApp

This way we can cleanup the resources in case deploying service mesh manifests because creating those in Generate phase leaves them hanging due to failing Delete hook

* fix(reconcile): corrects KfDef status in case of any error

Additionally propagates the error through reconcile to keep trying, as it was ignored.

* fix: reworks SMCP component readiness check

* chore: improves KfApp func docs

* chore: reworks logging in verifiers

* chore: simplifies CRD existence check

* chore: adds tests for feature enablement

* fix: sets interval for SMCP polling to 5s

* fix: handles types which are derived for built-in ones

for example `type InstallationMode string` was previously failing when
converting the default value defined in a custom tag. Now there's a
check performed and if value can be convereted to a given type it will.

In all other cases it will return an error.

* fix: sets default control plane installation mode rely on existing
installation

Proposed installation modes are:

- minimal
- pre-installed

Without this setting certain environments are not working,
as service account issuer might be set to different endpoint than kubernetes.default.svc

added logic to wait for the pods to be ready, otherwise patching IOR settings to disabled might not get updated when istio resources are created leading to duplicated route creation

and unifies logging by adding feature.Name to most of the logs

- autoformatting
- align with latest master changes

Co-authored-by: Bartosz Majsak <[email protected]>

reason: he is afk for next 2 weeks and will not be able to accept invite to the org, which potentially can make prow check unhappy

… cluster

without this fix we could fetch OdhDashboardConfig from different ns and try to perform an update on selected app ns, which leads to error and blocks operator from performing entire OSSM setup.

Oh well...

otherwise we create route for ns.domain but expects hosts to be opendatahub.domain which obviously does not work. Doh!

Creates ossm.env in each overlays/service-mesh of defined apps so that it can be used e.g. to overwrite configmap values

Co-authored-by: Cameron Garrison <[email protected]>

Co-authored-by: Cameron Garrison <[email protected]>