Skip to content

Conversation

@abrennan89
Copy link
Contributor

Fixes #978

  • Cleanup Knative services docs section

@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Apr 14, 2021
@knative-prow-robot knative-prow-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 14, 2021
Copy link
Contributor

@mpetason mpetason left a comment

Choose a reason for hiding this comment

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

Small updates. It looks good. The only thing I really saw was related to something that was written a while ago, that could be a little bit more clear - the image section. Other than that Service is lowercase in some areas and uppercase in others - for Kubernetes Service and Knative Service.

Copy link
Member

@evankanderson evankanderson left a comment

Choose a reason for hiding this comment

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

A few suggestions, but the move and rewrite overall looks good.

FWIW, it would be super-easy to review a file move (separate from content changes), but I realize that may be harder to handle on your end.

- name: TARGET
value: "Go Sample v1"
```
* `apiVersion`: The current Knative version.
Copy link
Member

Choose a reason for hiding this comment

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

Not sure why we call out apiVersion but not kind. Both of these should be stable in all these examples at this point.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

idk either, this was already there before I did the edits so I'd prefer not to block the PR on it since I think this whole bit could do with rewriting / reformatting to fit properly what we're doing now with "callouts" - can you maybe add a follow up issue for this?

Copy link
Member

Choose a reason for hiding this comment

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

If you don't want to rewrite this, I'm happy to have this be the place where we draw the line on updates.

@abrennan89
Copy link
Contributor Author

/approve

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 15, 2021
@pmbanugo
Copy link
Member

/lgtm

@knative-prow-robot
Copy link
Contributor

@pmbanugo: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

Copy link
Member

@evankanderson evankanderson left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

---

Knative Services are used to deploy an application. Each Knative Service is defined by a Route and a Configuration, which have the same name as the Service, contained in a YAML file. Every time the Configuration is updated, a new Revision is created.
To create an application using Knative, you must create a YAML file that defines a Knative service. This YAML file specifies metadata about the application, points to the hosted image of the app and allows the service to be configured.
Copy link
Member

Choose a reason for hiding this comment

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

I'm going to /lgtm and /approve, but I'm not sure about the "you must create a YAML file", since we also support using the kn CLI client and may have other mechanisms (web form?) in the future.

- name: TARGET
value: "Go Sample v1"
```
* `apiVersion`: The current Knative version.
Copy link
Member

Choose a reason for hiding this comment

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

If you don't want to rewrite this, I'm happy to have this be the place where we draw the line on updates.

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2021
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abrennan89, evankanderson

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:

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

@knative-prow-robot knative-prow-robot merged commit a4924d3 into knative:main Apr 15, 2021
@abrennan89 abrennan89 deleted the 978 branch May 3, 2021 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can't find docs on how to create cluster internal-only Knative service

5 participants