Redesign App Management

[vivekr-splunk]

Greetings everyone,

We're currently in the process of redesigning our App management system. As you're aware, the Splunk Operator currently supports App management through Amazon S3 or S3-API-compliant remote object storage locations. Customers upload apps to remote storage, and the Operator then downloads these images and copies them to Splunk containers. However, this approach has its limitations, such as the inability to ascertain the installed app's name as it may differ from the installation file's name.

1. We're seeking your input on designing a feature that enhances app management.

One idea we're considering is to introduce a metadata file in the S3 bucket that provides information about the apps, including:

• App name
• App package name
• Version

When the Operator copies these files, it will refer to the metadata file to install the package and update the CR status accordingly. Additionally, when an app is removed from the metadata file, it will be deleted from the Splunk instance and removed from the CR status.

We'd appreciate any alternative ideas or suggestions you may have.