Red Hat Advanced Cluster Management for Kubernetes vs. StorySlab

Well suited for - Large-scale Edge deployments of OpenShift instances. Policy-based consistency for all workloads is Less appropriate for - Small-scale deployments. Stand-alone deployments of K8s clusters. Deployments in the same data center.

I would recommend the app to another colleague if they were only going to manage 1-2 brands or channels. I believe in typical Eastman fashion, we had one idea of how we were going to use StorySlab and now a few years later our vision has changed. Items are starting to get cluttered.

Incentivized

• Continuous deployment of other OpenShift instances.
• Controls clusters and applications from a single console.
• Built-in Security & compliance.

• Customer Service
• Easy to use
• Low cost

Incentivized

• Initial deployment of the ACM itself needs to be made easy.
• Dependency on the Software versions of underlying open shift workloads during upgrades.
• LCM of ACM itself.

• Sign Up Process
• Clean up data
• Proactively send out metrics

Incentivized

I have also used TNA by Google Cloud, but that is not mature enough as ACM. Right now, ACM is the best choice as a cluster manager for private cloud data centers.

We use Marcom Central for one brand. They do not have a mobile app or mobile capabilities, which is unfortunate. We also use it as an e-commerce site for our customers to log on to as well.

Incentivized

• Reduced the deployment duration of individual nodes by 50%.
• Acts as a central manager for all the clusters.
• Provides a lot of infrastructure options (storage, networking, etc) to build instances of your choice.

• Positive- we took the responsibility off of reps to keep updated materials.
• Positive- easy to use.
• Negative- sometimes items show up unprecedented.

Incentivized