When Educates Platform is deployed via CLI, it uses a kapp label to identify generated resources. When Educates Platform is deployed via kapp-controller App, it uses the kapp App annotation on resources. Both applications will not be seen as the same and there will be errors if one deploys with one mechanism but then tries to use the other mechanism.
What should we do?
Nothing
Document
Prevent the CLI from installing if it detects the App is there
Prevent the App from installing if it detects resources already exist
Describe the bug
When Educates Platform is deployed via CLI, it uses a kapp label to identify generated resources. When Educates Platform is deployed via kapp-controller App, it uses the kapp App annotation on resources. Both applications will not be seen as the same and there will be errors if one deploys with one mechanism but then tries to use the other mechanism.
What should we do?
@GrahamDumpleton thoughts?
Additional information
No response