Add a possibility to check if the newly updated karydia config is already loaded into the karydia runtime via K8s natives. After this is implemented it should also be easier to write some more karydia config e2e-tests which should be added, as well.
User Story
As cluster admin I want to check if the karydia config is already loaded into the karydia runtime in order to know if the config gets already applied to new resources.
Implementation idea
Add an annotation or label to the karydia config resource after it is loaded into the karydia runtime and make sure it doesn't get reconciled only through this annotation / label update again because this would result in an endless loop if the annotation / label isn't allowed on update / creation time by the admission webhook.
Description
Add a possibility to check if the newly updated karydia config is already loaded into the karydia runtime via K8s natives. After this is implemented it should also be easier to write some more karydia config e2e-tests which should be added, as well.
User Story
As cluster admin I want to check if the karydia config is already loaded into the karydia runtime in order to know if the config gets already applied to new resources.
Implementation idea
Add an annotation or label to the karydia config resource after it is loaded into the karydia runtime and make sure it doesn't get reconciled only through this annotation / label update again because this would result in an endless loop if the annotation / label isn't allowed on update / creation time by the admission webhook.