Docs/custom domain

[adamkgray]

Update documentation related to setting up a custom domain for kfserving.

I made these changes after a conversation in the kfserving slack channel. I want to help clarify use-cases and motivations for future users. It personally took me a long time to find and apply this example doc.

So hopefully by updating the wording and adding some implementation context, others will be able to more quickly find and use these snippets.

Fixes:

• Remove path constraint from kf-serving.yml that breaks the intended functionality
• Update the verify example
• Add AWS example using ALB Ingress Controller

Release note:

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[kubeflow-bot]

This change is 

[k8s-ci-robot]

Hi @adamkgray. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[adamkgray]

@googlebot I signed it!

[adamkgray]

/assign @animeshsingh

[pugangxa]

/lgtm

[yuzisun]

/ok-to-test

[yuzisun]

/retest

[yuzisun]

/retest

[yuzisun]

/retest

[yuzisun]

/retest

[k8s-ci-robot]

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

Test name	Commit	Details	Rerun command
kubeflow-kfserving-presubmit	fa407e4	link	/test kubeflow-kfserving-presubmit

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.

[adamkgray]

Tfw you just update the docs but it makes the tests fail. Did i fork the wrong branch?

[yuzisun]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yuzisun

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 [yuzisun]

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

[yuzisun]

@adamkgray Thanks for

Tfw you just update the docs but it makes the tests fail. Did i fork the wrong branch?

No, your PR is all good just we had some gcloud issues lately for the CI.

Thanks for the doc contribution @adamkgray, this is really helpful!