You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/modules/ROOT/pages/01-setup.adoc
+14-20Lines changed: 14 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,58 +6,52 @@ include::_attributes.adoc[]
6
6
7
7
The following CLI tools are required for running the exercises in this tutorial. Please have them installed and configured before you get started with any of the tutorial chapters.
<1> Makes Knative to always run the latest revision of the deployment
50
-
<2> It is very important that the image is a fully qualified name docker image name with tag. For more details on this xref:ROOT:faq.adoc#faq-q2[Question 2 of FAQ]
49
+
<1> Makes Knative always run the latest revision of the deployment
50
+
<2> It is very important that the image is a fully qualified docker image name with tag. For more details on this, see xref:ROOT:faq.adoc#faq-q2[Question 2 of FAQ]
51
51
52
-
The service could be deployed using the command:
52
+
The service can be deployed using the following command:
The last curl command should return a response like**Hi greeter => '6fee83923a9f' : 1**
107
+
The last http command should return a response containing a line similar to**Hi greeter => '6fee83923a9f' : 1**
91
108
92
-
NOTE: Sometimes the response might not be returned immediately especially when the pod is coming up from dormant state, at those times try giving request again
109
+
NOTE: Sometimes the response might not be returned immediately especially when the pod is coming up from dormant state. In that case, repeat service invocation.
When the service was invoked with `curl -H "Host:greeter.knativetutorial.example.com" $IP_ADDRESS`,you noticed that we added a **Host** header to the request with value `greeter.knativetutorial.example.com`,this FQDN is automatically assigned to your Knative service by the Knative Routes,it uses the format like`**<service-name>.<namespace>.<domain-suffix>**`.
131
+
When the service was invoked with `http $IP_ADDRESS 'Host:greeter.knativetutorial.example.com'`, you noticed that we added a **Host** header to the request with value `greeter.knativetutorial.example.com`. This FQDN is automatically assigned to your Knative service by the Knative Routes and uses the following format:`**<service-name>.<namespace>.<domain-suffix>**`.
As Knative follows https://12factor.net[12-Factor] application principles, any new https://12factor.net/config[configuration] change will trigger new revision of the deployment.
150
+
As Knative follows https://12factor.net[12-Factor] application principles, any https://12factor.net/config[configuration] change will trigger creation of a new revision of the deployment.
134
151
135
152
To deploy a new revision of the greeter service, we will add an environment variable to the existing service as shown below:
<<basics-invoke-service,Invoking Service>> will now show an output like **Namaste greeter => '6fee83923a9f' : 1**, where __Namaste__ is the value that we configured via environment variable in the Knative service resource file.
203
+
, you will see two of them, named similar to `greeter-cqgcf` and `greeter-nsrbr`.
204
+
205
+
<<basics-invoke-service,Invoking Service>> will now show an output like **Namaste greeter => '6fee83923a9f' : 1**, where __Namaste__ is the value we configured via environment variable in the Knative service resource file.
183
206
184
207
[#basics-pinning-revision]
185
-
== Pinning service to a revision
208
+
== Pinning Service to a Revision
186
209
187
-
As you noticed that the Knative services always routes the traffic to the **latest** revision of the service deployment, thats because of the **runLatest** attribute in <<basics-service-rev2,service resource file>>.
210
+
As you noticed, Knative service always routes traffic to the **latest** revision of the service deployment, due to the **runLatest** attribute in the <<basics-service-rev2,service resource file>>.
188
211
189
-
Let us now make the greeter service use first revision created i.e. the one using the default `MESSAGE_PREFIX`.
212
+
Let us now make the greeter service use the first revision created, the one using the default `MESSAGE_PREFIX`.
190
213
191
214
[TIP]
192
215
====
193
-
You can use the get <<basics-show-knative-revisions, show knative revisions>> command to find the available revisions for the greeter service.
216
+
You can use the <<basics-show-knative-revisions, show Knative service revisions>> command to find the available revisions for the greeter service.
194
217
====
195
218
196
219
=== Service pinned to first revision
@@ -222,20 +245,20 @@ spec:
222
245
path: /healthz
223
246
----
224
247
225
-
<1> The **release** attribute in service resource file will make Knative use the revision specified in the **revisions** attribute.
248
+
<1> The **release** attribute in the service resource file will make Knative use the revision specified in the **revisions** attribute.
226
249
227
250
[IMPORTANT]
228
251
====
229
-
The value of revisions might be different in your setup
252
+
The names of revisions may be different in your setup
230
253
====
231
254
232
-
Let redeploy the greeter service by pinning it to the first revision that was created:
255
+
Let us redeploy the greeter service by pinning it to the first revision that was created:
0 commit comments