Frontend Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, single container deploying all components
• npm run start
• Other (please specify below)

Backend (Jet Stream) Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, single container deploying all components
• Other (please specify below)

Deployed the all-in-one-container to PCF using CF Push.

Expected behaviour

I expected the metrics for things like running applications and memory usage to match what I see in Pivotal's Apps Manager product.

Actual behaviour

The metrics are drastically different. For example in one of our org-space combos, we have 219 Apps deployed, 117 of which are running, using up ~243 GB out of a 300 GB quota.

When I look at the same org-space combo in Stratos, I see only 26 applications using ~29 GB out of a 300 GB quota.

Steps to reproduce the behavior

Deploy container into a larger PCF foundation and examine irregularities.

Context

This level of inaccuracy would be a deal breaker on trying to replace Apps Manager with Stratos for interacting / observing PCF foundations.

Possible Implementation