Skip to content
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.

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

guide updates for knative quick start update #7100

Merged
merged 1 commit into from
Feb 21, 2020

Conversation

kameshsampath
Copy link
Contributor

The guide has been updated for the quarkusio/quarkus-quickstarts#112

Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I added a bunch of comments, can you have a look?

or https://knative.dev/v0.6-docs/install/knative-with-minishift/[Minishift]


* having access to a Kubernetes cluster. Minikube are valid options.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* having access to a Kubernetes cluster. Minikube are valid options.
* having access to a Kubernetes cluster. Minikube is a valid option.

This guide covers:

* The deployment of the application to Kubernetes
* The deployment of the application to Knative
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe let's remove the bullet list if you have only one item (and add a dot at the end of the sentence)?

@@ -39,106 +36,95 @@ Clone the Git repository: `git clone {quickstarts-clone-url}`, or download an {q

The solution is located in the `getting-started-knative` directory.

== Deploying the application in Knative
== Setup Kubernetes Cluster
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
== Setup Kubernetes Cluster
== Set up Kubernetes Cluster

====
If you are not using private GitHub repo then you dont need the `Deploy Key` created and added to the Build Service Account
====
<1> Make the current docker context to be that of minikube
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<1> Make the current docker context to be that of minikube
<1> Make the current Docker context to be that of minikube

using Dockerfile and https://github.com/GoogleContainerTools/kaniko[Kaniko]. After a successful build you will have the
Knative serving application deployed with the built container image. You can watch the application build pods using the
command `kubectl get pods -w`. You can terminate the watch using the command kbd:[CTRL + c]
== Setup Nexus(Optional)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
== Setup Nexus(Optional)
== Set up Nexus (Optional)

and copy them to `${project.build.directory}/knative`

Run the following command to create the Knative resources:
It is very important to note that the Dockerfile in src/main/docker folder has been modified to support
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to support what?

----

== Accessing your application
As it will take few minutes for the build and deploy to be completed you can watch the status using:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As it will take few minutes for the build and deploy to be completed you can watch the status using:
As it will take a few minutes for the build and deployment to complete, you can watch the status using:

greeter-deployment-5749cc98fc-gs6zr 2/2 Running 10s
----

NOTE: The deployment name could differ in your environment
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
NOTE: The deployment name could differ in your environment
NOTE: The deployment name could differ in your environment.


The application is now exposed as an internal service. If you are using `minikube` or `minishift`, you can access it using:
A successful Knative Service deployment will show the following pods in the current namespace:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A successful Knative Service deployment will show the following pods in the current namespace:
A successful Knative service deployment will show the following pods in the current namespace:


NOTE: The deployment name could differ in your environment

Once the Knative service is successfully running, you can call the service it using the script `./bin/call.sh`, which should return a response like `hello`. Allowing it to idle for approximately 60-65 seconds -- that is without any further requests --, you will see it automatically scales down to zero pods.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Once the Knative service is successfully running, you can call the service it using the script `./bin/call.sh`, which should return a response like `hello`. Allowing it to idle for approximately 60-65 seconds -- that is without any further requests --, you will see it automatically scales down to zero pods.
Once the Knative service is successfully running, you can call the service using the script `./bin/call.sh`, which should return a response like `hello`. Allowing it to idle for approximately 60-65 seconds - that is without any further requests -, you will see it automatically scales down to zero pods.

@kameshsampath
Copy link
Contributor Author

@gsmet thank you for quick review, I have updated your comments and pushed it back . It will be great of you can check and merge the related code quarkusio/quarkus-quickstarts#112

@gsmet
Copy link
Member

gsmet commented Feb 17, 2020

@kameshsampath I think you missed the hidden ones (there are 9 of them hidden by GH). At least they are not marked as outdated.

@kameshsampath
Copy link
Contributor Author

@gsmet

@kameshsampath I think you missed the hidden ones (there are 9 of them hidden by GH). At least they are not marked as outdated.

Not sure how I missed them , sorry about. They are all addressed in the latest commit.

@gsmet gsmet merged commit c96c7ee into quarkusio:master Feb 21, 2020
@gsmet
Copy link
Member

gsmet commented Feb 21, 2020

Squashed and merged, thanks!

@gsmet gsmet added this to the 1.3.0 milestone Feb 21, 2020
@kameshsampath kameshsampath deleted the issue-112-docs branch February 21, 2020 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants