Dnspolicy create

[david-martin]

Part of #30 (the create part)

There's a lot in the create page because of the optional top level fields for healthCheck and loadBalancing (which is based on setting routingStrategy to loadbalanced).
The other top level fields are less complex:

• name
• namespace (uses a namespace dropdown)
• targetRef (uses a gateway dropdown by listing all gateways in the cluster)

TODO:

• namespace bar in top of page (which sets the namespace dropdown automatically on first load)
• alert modal on create error
• allow for matchLabels as an alternative to matchExpressions under weighted.custom[].selector
• i18n in numerous places
• Radio options for Create via: form / yaml
• sync fields between form and yaml
• Link for how 'to create an additional Gateway'
• wire up 'Create DNSPolicy' button on policy listing page to this new page
• follow up Validation of form inputs before attempting to submit the policy - this happens automatically for the yaml editor component.
• follow up Reuse view for 'update'
• follow up styling improvments for the custom weights selectors
• follow up Add support for providerRefs field

Screenshots

Initial Create page

Expanded page

Yaml editor

[jasonmadigan]

small thing, but I guess this applies to all of these views - should we have a helper to fetch the latest apiVersions for our resources? saves us having to deal with drift here (well, for the most part). I guess ditching the apiVersion would do the same.

[jasonmadigan]

LGTM.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: david-martin, jasonmadigan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [david-martin,jasonmadigan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jasonmadigan]

/lgtm