syn2mas will not procced / fail dry run when warnings are present (with no way to bypass)

[Half-Shot]

Describe the bug

I tried to migrate my homeserver to MAS following the process but found that I had some warnings (harmless, overall):

===== Warnings =====
These potential issues should be considered before migrating from Synapse to MAS right now:

• Synapse database contains 71147 guests which will be migrated are not supported by MAS. See https://github.com/element-hq/matrix-authentication-service/issues/1445

• Synapse database contains 3 non-email 3PIDs (probably phone numbers), which will be migrated but are not supported by MAS.

Error from server (BadRequest): container "syn2mas-migrate" in pod "matrix-syn2mas-8gs5f" is waiting to start: PodInitializing

which causes MAS to exit with an exitcode 11 which means the migration cannot proceed. I can't see an exposed way to override this.

Expected behavior

I'd like to be able to migrate in spite of the warnings.

Additional context

This is ESS 26.1.0

[gaelgatelement]

What happens if you use dryRun=false ? If the deployment markers are preventing you to continue, you can disable them with deploymentMarkers.enabled=false. They are here to prevent you from doing unwarranted things, but in your case I think its fine.

[Half-Shot]

What happens if you use dryRun=false

I found the check init container would still fail, and so even with dryRun off I couldn't progress.

In the end I solved this by (brace yourself):

• Resetting my deploymentMarkers to a sane value (I forget what)
• Copying the Job and removing the check container.
• Running the migration
• Manually setting the deploymentMarker to the value it usually sets after migration (also forgot what this was)

I think having dryRun=false report the warnings but not prevent the migration job from running would have been my ideal soln. The problem was the check job reports a statusCode of 11 on warnings which kube treats as a fail.