pissman

I wrote an automated tool to migrate all my ECS tasks to deployment files (seperated by Deployment, Service, SA and Ingress) just to get a running start. I'll have a look at Kustomize, thanks for the heads up!

• Yes, I guess you're right. shit.management is a good domain name.
• I guess I'll find out when I get there, still at a beginning of a deployment pipeline
• I am using deployment manifests. Not too sure what Kustomize is, I'm still quite a noob

• Yes, I guess the rollout will be dev -> Preproduction (environment that equivalent to production) -> Production
• No downtime, but why would that be an issue? I make a deployment, old pod goes down, new pod goes up.
• That is mostly my job. My manager suggested I calculate the cost of moving the containerized services outside the instance and have them run on the cluster in a separate namespace (meaning 1 namespace for every developer).

No gods, no masters!

The decision will be based upon the parameters you mentioned, with a focus on cost, so they are a bit hard to ignore :)

Oh shit! SO much better!

Thanks!

Yes, that's what I'm wondering. I'm seeing reports of people saying it works fine. Perhaps you should give it another go after all these years and report back on performance here so we can try and isolate the issue!

I've tested it before the 2.5 SteamVR major update and after, with seemingly no improvements.

Please let me know if you find it!

I just did, seems like there's no difference. Is there somewhere I need to enable it?