From looking around the web a bit, it seems like for both Motioneye and Frigate misconfigurations can lead to high cpu usage. It might be worth your time to compare settings (on TN and in app) between the two deployments and see if there are any differences. If you were able to roll back to the DF boot environment, I’d expect you should be able to do so to the EE one as well. You might be able to reach out for help upstream at the app projects themselves.
It’s possible that there is a bug related to how we’ve migrated the settings or set defaults on the new catalog. It’s also possible that they’re configured the same but one of those settings responds differently on docker than it does on the K8s chart.
Edit: Based on your other thread, the switch in Frigate versions may have contributed to this as well. The EE catalog is on 0.14.1, so if you’re comparing that to a 0.13.X version in DF that may play in. Based on a quick search there were a few reports of increased CPU use after 0.14–though it seems to be very system and settings dependent.