Skip to content

Issue fixes for #19438 and #19437 #21008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2020
Merged

Issue fixes for #19438 and #19437 #21008

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions modules/interacting-serverless-apps-http2-gRPC.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,14 @@ To do this you must find the ingress gateway's public address and the applicatio
. The ingress gateway's public address can be determined using this command:
+
----
oc -n istio-system get svc istio-ingressgateway
$ oc -n knative-serving-ingress get svc kourier
----
+
The output will be similar to this example:
+
----
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
istio-ingressgateway LoadBalancer 172.30.51.103 a83e86291bcdd11e993af02b7a65e514-33544245.us-east-1.elb.amazonaws.com 80:31380/TCP,443:31390/TCP,31400:31400/TCP,15029:30672/TCP,15030:30970/TCP,15031:32657/TCP,15032:32400/TCP,15443:30167/TCP,15020:32285/TCP 67m
kourier LoadBalancer 172.30.51.103 a83e86291bcdd11e993af02b7a65e514-33544245.us-east-1.elb.amazonaws.com 80:31380/TCP,443:31390/TCP 67m
----
+
The public address is surfaced in the `EXTERNAL-IP` field, and in this case would be:
Expand Down
4 changes: 2 additions & 2 deletions modules/verifying-serverless-app-deployment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,13 @@
[id="verifying-serverless-app-deployment_{context}"]
= Verifying your serverless application deployment

To verify that your serverless application has been deployed successfully, you must get the application host created by Knative, and then send a request to that host and observe the output.
To verify that your serverless application has been deployed successfully, you must get the application URL created by Knative, and then send a request to that URL and observe the output.

NOTE: If you changed the application name from `helloworld-go` to a new name when creating the `service.yaml` file, replace `helloworld-go` in the commands with the new name you created.

.Procedure

. Find the application host.
. Find the application URL.
+
----
oc get ksvc helloworld-go
Expand Down