It would benefit everyone if the installer rejects unrecognized properties in install-config.yaml before creating resources.

Right now, we do some validation (e.g. tab instead of white space) but if entries are not accessible (wrong name, values) - we kick off install process, create resources then fail (sometimes after waiting through all the timeouts)

In scope:

• validate format
• verify key names are what we are expecting (we ignore values we don't use and act as pass through)
• verify key values are what we are expecting
• verify the entries are accessible (e.g. sufficient permission for creating resources based on the entered value)