Yes there is. HTTP/2 has SETTINGS frame to communicate implementation capabilities, and SETTINGS_ENABLE_PUSH is standardized to communicate push support. Chrome will send SETTINGS_ENABLE_PUSH set to zero, so no user agent parsing is necessary and all compliant implementations should handle this transition transparently.
Or are we just going to end up with servers pushing to chrome and it just ignoring it? That sounds even worse.