Evolves the Gateway Name field

[danehans]

Evolves the following Gateway fields:

• Name used for generating a listener wildcard certificate when unspecified by the TLS configuration.
• Certificate godocs.

Partially fixes #49

/assign @bowei

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: danehans
To complete the pull request process, please assign thockin
You can assign the PR to them by writing /assign @thockin in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

@danehans: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-service-apis-docs	f78c8e0	link	/test pull-service-apis-docs

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[jpeach]

I think that we should separate changes to certificate handling into its own PR, with use cases and all the rest. I would expect there to be a range of opinions around wildcard certificates :)

[jpeach]

I don't see any mention of wildcard certificates elsewhere in the spec. If this is a new feature, we should first capture a use case and then propose it independently.

[jpeach]

I think that wildcard certificate handling should be proposed and discussed as an independent item. Generating wildcard certificates is something that ought to require explicit configuration, and I don't think that it should happen as a side-effect of naming a listener.

I'll also note that many ingress controllers don't generate certificates, so I'm not sure the the spec should place requirements on them to do so.

[danehans]

/hold

for resolution to #75

[danehans]

Superseded by #76