* Simplify Node.js package.json
Since this is a Hello World, I do not think we need the `homepage`, `bugs` and `repository` attributes of package.json, but instead I suggest to keep it short in order to show the actual simplicity of the sample
* README missed the dependencies
* add v0.1 release branch
and provide some indication that the website is coming
* Update doc-releases.md
Co-Authored-By: RichieEscarez <rescarez@google.com>
* temporarily move the TBD link to the bottom
* Document default channels for users and operators
Features described were added in
https://github.com/knative/eventing/pull/580.
* Link to default-channels.md in eventing README
Adds a Configuration heading for topics unrelated to Getting Started.
* Briefly describe default channels in heading
Co-Authored-By: grantr <grantr@gmail.com>
* Update in response to feedback
Better README flow.
Explain why default channels can't have arguments.
* Update kube-version to 1.10.7
```
knative1 $ ibmcloud cs cluster-create --name=$CLUSTER_NAME \
> --zone=$CLUSTER_ZONE \
> --kube-version=1.10.3 \
> --machine-type=b2c.4x16 \
> --workers=3
Creating cluster...
FAILED
A previous patch was specified. Only the most recent patch for a particular minor version can be specified during cluster-create. To list supported Kubernetes versions, run 'ibmcloud ks kube-versions'. (E0156)
Incident ID: 5533234a-df08-478b-b298-ab0ddbe67dfe
knative1 $ ibmcloud ks kube-versions
OK
Version
1.8.15 (deprecated, unsupported in 9 days)
1.9.10
1.10.7 (default)
1.11.2
To assess the differences across versions, see https://console.bluemix.net/docs/containers/cs_versions.html#cs_versions.
```
After change:
```
knative1 $ ibmcloud cs cluster-create --name=$CLUSTER_NAME \
> --zone=$CLUSTER_ZONE \
> --kube-version=1.10.7 \
> --machine-type=b2c.4x16 \
> --workers=3
Creating cluster...
OK
```
* No longer use --kube-version to avoid need to change instructions
* Update Knative-with-IKS.md
Explains parameters like `build.knative.dev/git-0` under the examples.
This could be explained _somewhat_ more in the comments in the examples
themselves. If we think that approach would be preferable, I'm happy to
update this.
* Add a tutorial for writing an event source
Also published at https://github.com/grantr/event-source-the-hard-way.
Reference code at https://github.com/grantr/sample-source.
Currently only goes through writing the controller. Writing a dispatcher
is TODO.
* Add SampleSource as a MetaSource
Not sure if this counts as a meta source, but it's not a real source
either. Maybe there should be a category for example sources?
* Update for review feedback
Labs now called Steps
Move tools section to readme
Move create repo to bootstrap
Move alternatives section to end of readme
Delete empty step
* Fix typo
* Update for feedback
Reword target audience sentence.
Move TODO to a comment so it's invisible.
Mention more clearly the existing sink resolution helpers.
* Link to knative code when it's referenced
* Update docs to use correct ingress gateway service.
* Update wording of knative-ingressgateway deprecation.
* Update wording of knative-ingressgateway deprecation per feeeback.
eventing.yaml doesn't install the in-memory provisioner, release.yaml
does. Since the provisioner is required to run the samples, we should be
telling users to install release.yaml.
* Add link to image in Dockerhub
Mainly for consistency with other samples.
* also README
* Fixes indentation issue causing build test failure
* fix bullet list indentation
* attempt #2 -- fixing build failure
* Add a note about enabling outbound access
* fix bold tags
* more rejiggering
* deal with existing lint issues, change to header as per linter
* remove subheader
This is a 15 line trivial hello world, a 15 line license header adds unnecessary complexity.
Many other samples do not include a license header.
The license is already captured at the root of the repository.