I have to login to PCF to check environments or add services to bind to an app.
The CF cli is not very easy to understand compared to aws eb cli or herokus toolbelt
The login screen says "email" but you actually have to enter your user ID
Devops become your enemies, especially if they lock down PCF environments. I don't want to beg for a redis tile.
PCF eats a lot of ram from our virtual servers.
The PCF support is layered with different urgency levels, most of the time they ignore you or are slow to respond
Basically I think it's a tool that gets in the way of developers and gives headaches to the platform team. However my company signed a contract with them, so we're tied in for a year.... I might quit before then
You could squeeze them onto one VM, but that would require that CF teams cooperate on manifests. Inconceivable!
The CF team is a bunch of Pivots... they cooperate quite well and probably better than most other teams, especially since they rotate across projects fairly often. Disclosure, I worked on CF in the early days, on a number of teams.
Cloud Foundry (PAS) is not designed to be used this way -- it had multitenancy designed in from the beginning.
For PKS the idea of cluster-per-project makes more sense, given that Kubernetes doesn't reaaaally have multitenancy in the same sense.
We have low timeouts on most logins anyway, so having it on PCF isn’t a big deal.
We have a CI/CD workflow, so I don’t really have to login to the CLI that much.
Locked down environments are always a pain - but it would be no different if your org locked down AWS or Heroku, which they could.
You're doing devops wrong, which may explain why you're having a bad time with the platform.
> I have to login to PCF to check environments or add services to bind to an app.
You should automate this with CI servers and pipelines.
The complaints about RAM usage and support service I agree with.
It sounds like your organisation is disfunctional, and its treatment of PCF is the symptom not the cause.
PCF itself is also very expensive. I'm not sure if they charge per node or per app; they've changed it over the last few years. I would get the skinny on that before committing to anything and do a TCO/ROI analysis.
If you are going to go this route, I would also consider doing a PoC with OpenShift or Rancher. These are managed Kubernetes offerings, both on prem. Both have free open-source editions that mostly mirror what you'll get in the Enterprise offering at smaller scale. Rancher is also less "enterprisey" in that they aren't as aggressive about enterprise support or upsells, at least from what I've heard.
I think you'll be locked into big contracts with either option, but Pivotal's lock-in is tighter, at least from what I can tell. This could change after IBM fully moves in, however.