Skip to content

Commit

Permalink
Merge website files into Master (knative#1025)
Browse files Browse the repository at this point in the history 
* Add front matter to Build files (knative#833)

* Update README.md

* Adding front matter to builds.md

* Update installing-build-component.md

* Update README.md

Revert changes so Richie can handle this with the index file

* Update builder-contract.md

* Update personas.md

* Update auth.md

* Update creating-builds.md

* Update build-templates.md

* sentence case

* sentence case

* sentence case

* Adding frontmatter to /install/ (knative#834)

* Adds front matter to Serving (knative#838)

* Update accessing-logs.md

* Update accessing-metrics.md

* Update accessing-traces.md

* Update cluster-local-route.md

* Update debugging-application-issues.md

* Update debugging-performance-issues.md

* Update gke-assigning-static-ip-address.md

* Update installing-logging-metrics-traces.md

* Update outbound-network-access.md

* Update setting-up-a-logging-plugin.md

* Update using-a-custom-domain.md

* Update using-an-ssl-cert.md

* Update using-cert-manager-on-gcp.md

* Update using-external-dns-on-gcp.md

* site index for fluentd folder (knative#839)

* add Hugo index files and frontmatter (knative#840)

* hugo build files for autogen refdocs (knative#841)

* move resources and readme (knative#843)

* site: add blog (knative#837)

* add blog folder

* switch to sentence case

* site: add community and contributing (knative#836)

* add _index.md files and front matter

* switch to sentance case caps

* fix weights

* Update community/samples/README.md

Co-Authored-By: RichieEscarez <[email protected]>

* site: restructure content into a "docs" directory (knative#842)

* move content into a 'docs' directory

* inject additional 'docs' directory

* site: add build files and front matter to serving samples (knative#850)

* new _index.md files and front matter

* serving samples + fix urls

* remove file

* add PR#851 - channels (knative#853)

* Update README.md (knative#854)

* Remove README.md from all links (knative#855)

* Remove README.md from all links

* mend

* mend

* mend

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* fix links in community (knative#857)

* Update _index.md (knative#856)

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

Adds missing pointer to README

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* revert

* fix build links (knative#858)

* site: fix eventing links (knative#859)

* fix eventing links

* Update README.md

* fix install links (knative#860)

* site: fix serving links (knative#861)

* fix serving links

* Update using-external-dns-on-gcp.md

* remove hardcoded github link (knative#863)

* Update README.md (knative#864)

Fix links by removing md file extensions.

* Fix links (knative#866)

* Fix links

* Update installing-build-component.md

* Update builder-contract.md

* add missing hello-world directory (knative#865)

* Link fixes for Build (knative#867)

* Fix links

* Update installing-build-component.md

* Update builder-contract.md

* Update creating-builds.md

* Update builder-contract.md

* Update builds.md

* Update creating-builds.md

* Update installing-build-component.md

* Update installing-build-component.md

* Update creating-builds.md

* Update creating-builds.md

* Update builds.md

* Update build-templates.md

* convert to Hugo rel link

* Manually run prettier.io (knative#880)

* Manually run prettier.io

Trying to fix the stuff that hits prettier.io bugs.

* Fix prettier.io issues.

* Revert manual link fixes (use new build script instead) (knative#927)

* Revert "convert to Hugo rel link"

This reverts commit f1bbc8e.

* Revert "Fix links (knative#866)"

This reverts commit 3a57ffe.

* Revert "remove hardcoded github link (knative#863)"

This reverts commit fb7fdd9.

* Revert "site: fix serving links (knative#861)"

This reverts commit f61514c.

* Revert "fix install links (knative#860)"

This reverts commit 1fcf32b.

* Revert "site: fix eventing links (knative#859)"

This reverts commit 8809165.

* Revert "fix build links (knative#858)"

This reverts commit 847e08b.

* Revert "fix links in community (knative#857)"

This reverts commit 0cd5a44.

* Revert "Remove README.md from all links (knative#855)"

This reverts commit 2029c8b.

* Revert "Update README.md (knative#864)"

This reverts commit 072c731.

* Adding frontmatter to Gloo guide (knative#939)

*  adding frontmatter; cherry-picking commit into 0.3 (knative#943)

* Deploy using private registry (knative#847)

* new doc for deploying with private registry

* update last few steps

* header sizes

* capitalization

* updating with correct registry annotation and small edits

* wording

* formatting

* formatting

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* update based on feedback

* missing <

* adding tic marks for filename

* udpate with helloworld-go sample

* add testing application

* update return from helloworld app

* update readme with link to doc

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* Update serving/deploying-with-private-registry.md

Co-Authored-By: beemarie <[email protected]>

* adding frontmatter; cherry-picking commit into 0.3

* Update Knative-with-Minishift.md (knative#988)

Update to correct title (Openshift > Minishift), as mentioned by Ashleigh in the Docs WG.

* add type:docs + enable relative links (knative#990)

* Deleting an unnecessary file

accidentally copied in extra file

* update ref docs api build script and files (knative#997)

* all links must have ./ (knative#1004)

* all links must have ./

* Update contributing/README.md

Co-Authored-By: RichieEscarez <[email protected]>

* Update contributing/README.md

Co-Authored-By: RichieEscarez <[email protected]>

* Update for clarity

* Update README.md

Fixing my poorly formatting suggestion

* ref tool steps + script (knative#1008)

* Incorporate edits from knative#1008 (knative#1010)

* Incorporate edits from knative#1008

* Add "contributor" info link

* page-by-page link check fixes (knative#1024)

* update readmes - source and site versions

* rename file to fix left nav

* rename file and remove folder to fix left nav
  • Loading branch information
@RichieEscarez @knative-prow-robot
RichieEscarez authored and knative-prow-robot committed Mar 20, 2019
1 parent 2a55e5c commit 3c04f86
Show file tree
Hide file tree
Showing 239 changed files with 2,381 additions and 1,096 deletions.
1 change: 1 addition & 0 deletions .gitignore
View file
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
.DS_Store
.idea/

14 changes: 14 additions & 0 deletions README.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Welcome to the source file repository for Knative documentation

## View published docs

Use the [Knative Documentation website](http://www.knative.dev/docs) to view the
docs and learn about Knative.

## Source files

View the source files if you want to contribute a fix or add new content.
Each release of the Knative docs are
[branched](https://github.com/knative/docs/branches). If you are looking for an
archived doc set, see the list of available versions in
[Knative doc releases](./doc-releases.md).
129 changes: 129 additions & 0 deletions _index.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,129 @@
+++
title = "Knative"

+++

{{< blocks/cover title="Welcome to the Knative Project!" image_anchor="top" height="max" color="dark" >}}
<div class="mx-auto">
<a class="btn btn-lg btn-primary mr-3 mb-4" href="{{< relref "/docs" >}}">
Learn More <i class="fas fa-arrow-alt-circle-right ml-2"></i>
</a>
<a class="btn btn-lg btn-secondary mr-3 mb-4" href="https://github.com/knative">
View Repository <i class="fab fa-github ml-2 "></i>
</a>
<p class="lead mt-5"><h2>Kubernetes-based platform to build, deploy, and manage modern serverless workloads.</h2></p>
<div class="mx-auto mt-5">
{{< blocks/link-down color="info" >}}
</div>
</div>
{{< /blocks/cover >}}


{{% blocks/lead color="primary" %}}
Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center.

{{% /blocks/lead %}}


{{% blocks/section %}}
<div class="col-12">
<h1 class="text-center">Essential base primitives for all</h1>
Knative components are built on Kubernetes and codify the best practices shared by successful real-world Kubernetes-based frameworks. It enables developers to focus just on writing interesting code, without worrying about the “boring but difficult” parts of building, deploying, and managing an application.
</div>
{{% /blocks/section %}}

{{% blocks/section %}}
<div class="col-12">
<h1 class="text-center">
Developer-friendly software</h1>
Knative offers a set of reusable components that focuses on solving many mundane but difficult tasks such as orchestrating source-to-container workflows, routing and managing traffic during deployment, auto-scaling your workloads, or binding running services to eventing ecosystems. Developers can even use familiar idioms, languages, and frameworks to deploy any workload: functions, applications, or containers.
</div>
{{% /blocks/section %}}

{{% blocks/section %}}
<div class="col-12">
<h1 class="text-center">Supports popular development patterns</h1>
Knative focuses on an idiomatic developer experience. It supports common development patterns such as GitOps, DockerOps, ManualOps, as well as tools and frameworks such as Django, Ruby on Rails, Spring, and many more.
</div>
{{% /blocks/section %}}

{{% blocks/section %}}
<div class="col-12">
<h1 class="text-center">Best of both worlds: Flexibility and control</h1>
Knative is designed to plug easily into existing build and CI/CD toolchains. By focusing on open-source-first technologies that run anywhere, on any cloud, on any infrastructure supported by Kubernetes, enterprises are free to move their workloads wherever they run best. This offers the flexibility and control customers need to adapt the system to their own unique requirements.
</div>
{{% /blocks/section %}}

{{% blocks/section %}}
<div class="col-12">
<h1 class="text-center">Operator-friendly</h1>
Knative is designed to be run as a service by all major cloud providers. Google currently works with industry leaders such as Pivotal, SAP, Red Hat, IBM, and many others to create the building blocks that will best suit the needs of developers. Knative powers real-world workloads and is also compatible with other cutting-edge technologies such as Kubernetes and Istio.
</div>
{{% /blocks/section %}}

<!----------
{{% blocks/section %}}
<div class="col-12">
<h1 class="text-center">Run your serverless workloads on Kubernetes Engine</h1>
You can now run your serverless workloads on Google Kubernetes Engine (GKE) by enabling the serverless add-on. Powered by Knative, the serverless add-on helps developers orchestrate builds, serving, and events with a single click, enabling the benefits of an idiomatic developer experience with the flexibility and control of GKE.
</div>
{{% /blocks/section %}}
---------->

{{< blocks/section >}}

<h1 class="text-center">Knative Features</h1>
<table align="center">
<thead>
<tr>
<th width="30%">Feature Name</th>
<th width="70%">Feature Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>Serving</td>
<td>Scale to zero, request-driven compute model</td>
</tr>
<tr>
<td>Build</td>
<td>Cloud-native source to container orchestration</td>
</tr>
<tr>
<td>Eventing</td>
<td>Universal subscription, delivery, and management of events</td>
</tr>
<!----------
<tr>
<td>Add-on for GKE</td>
<td>GCP managed stack on Kubernetes</td>
</tr>
----->
</tbody>
</table>

{{< /blocks/section >}}


{{< blocks/section color="light" >}}

{{% blocks/feature icon="fab fa-slack" title="Talk to us on Slack!" url="https://knative.slack.com/" %}}
Interested in learning more, speaking to other contributors, or finding answers?
{{% /blocks/feature %}}


{{% blocks/feature icon="fab fa-github" title="Contributions welcome!" url="./contributing/" %}}
Want to join the fun? New users are always welcome!
{{% /blocks/feature %}}


{{% blocks/feature icon="fab fa-twitter" title="Follow us on Twitter!" url="https://twitter.com/KnativeProject" %}}
For announcement of latest features etc.
{{% /blocks/feature %}}


{{< /blocks/section >}}




Binary file added background.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 12 additions & 0 deletions blog/_index.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
---
title: "Knative blog"
linkTitle: "Blog"
menu:
main:
weight: 30
---


Welcome to the Knative **blog** section. Keep up-to-date with product and
release announcements, read articles, hear about recent social events, and
find out where the Knative team will be talking next.
18 changes: 18 additions & 0 deletions ...ticles/Build--deploy--manage-modern-serverless-workloads-using-Knative-on-Kubernetes.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: "Build, deploy, manage modern serverless workloads using Knative on Kubernetes"
linkTitle: "Serverless workloads using Knative"
date: 2018-11-14
description: "Learn how to build, deploy, and manage modern serverless workloads using Knative on Kubernetes."
---

<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><article class="h-entry">
<section data-field="subtitle" class="p-summary">
By now, Kubernetes should be the default target for your deployments. Yes, there are still use-cases where Kubernetes is not the optimal…
</section>
<section data-field="description" class="p-summary">
By now, Kubernetes should be the default target for your deployments. Yes, there are still use-cases where Kubernetes is not the optimal…
</section>
<section data-field="body" class="e-content">
<section name="f298" class="section section--body section--first section--last"><div class="section-divider"><hr class="section-divider"></div><div class="section-content"><div class="section-inner sectionLayout--insetColumn"><h3 name="a5fb" id="a5fb" class="graf graf--h3 graf--leading graf--title">Build, deploy, manage modern serverless workloads using Knative on Kubernetes</h3><p name="6981" id="6981" class="graf graf--p graf-after--h3">By now, <a href="https://kubernetes.io/" data-href="https://kubernetes.io/" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">Kubernetes</a> should be the default target for your deployments. Yes, there are still use-cases where Kubernetes is not the optimal choice, but these represent an increasingly smaller number of modern workloads.</p><p name="c063" id="c063" class="graf graf--p graf-after--p">The main value of Kubernetes is that it greatly abstracts much of the infrastructure management pain. The broad support amongst virtually all major Cloud Service Providers (CSP) also means that your workloads are portable. Combined with the already vibrant ecosystem of Kubernetes-related tools, means that the experience of the operator, the person responsible for managing Kubernetes, is now pretty smooth.</p><blockquote name="c1ac" id="c1ac" class="graf graf--blockquote graf-after--p">But what about the experience of the developer, the person who builds solutions on top of Kubernetes?</blockquote><p name="09a5" id="09a5" class="graf graf--p graf-after--blockquote">Despite what some might tell you, Kubernetes is not yet today’s application server. For starters, the act of developing, deploying and managing services on Kubernetes is still too complicated. Yes, there are many open source projects for logging, monitoring, integration, etc., but, even if you put these together just right, the experience of developing on Kubernetes is still fragile and way too labour-intensive.</p><p name="1312" id="1312" class="graf graf--p graf-after--p">As if that wasn’t enough, the growing popularity of functions as the atomic unit of code development further contributes to the overall complexity. Often creating different development patterns on two disconnected surface areas:one for functions (FaaS) and one for applications (PaaS).</p><p name="3f53" id="3f53" class="graf graf--p graf-after--p">As the result, developers today are being forced to worry about infrastructure-related concerns: such as, image building, registry publishing, deployment services, load balancing, logging, monitoring, and scaling. However, what all they really want to do is write code.</p><h3 name="33f0" id="33f0" class="graf graf--h3 graf-after--p">Introducing Knative</h3><figure name="69ac" id="69ac" class="graf graf--figure graf--layoutOutsetLeft graf-after--h3"><div class="aspectRatioPlaceholder is-locked" style="max-width: 410px; max-height: 322px;"><div class="aspectRatioPlaceholder-fill" style="padding-bottom: 78.5%;"></div><img class="graf-image" data-image-id="1*pRrZVrsz5zNyg4AuWGLa3Q.png" data-width="410" data-height="322" src="https://cdn-images-1.medium.com/max/600/1*pRrZVrsz5zNyg4AuWGLa3Q.png"></div></figure><p name="aa9b" id="aa9b" class="graf graf--p graf-after--figure">At Google Cloud Next in San Francisco this week, Google announced an early preview of the GKE serverless add-on (<a href="http://g.co/serverlessaddon" data-href="http://g.co/serverlessaddon" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">g.co/serverlessaddon</a>). Google also open-sourced Knative (kay-nay-tiv), the project that powers the serverless add-on (<a href="https://github.com/knative" data-href="https://github.com/knative" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">github.com/knative</a>).</p><p name="7c8f" id="7c8f" class="graf graf--p graf-after--p">Knative implements many of the learnings from Google. The open source project already has contributions from companies like Pivotal, IBM, Red Hat and SAP and collaboration with open-source Function-as-a-Service framework communities like <a href="https://github.com/apache/incubator-openwhisk" data-href="https://github.com/apache/incubator-openwhisk" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">OpenWhisk</a>, <a href="https://github.com/projectriff/riff" data-href="https://github.com/projectriff/riff" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">riff</a>, and <a href="https://github.com/kyma-project" data-href="https://github.com/kyma-project" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">Kyma</a> who either replatform on to Knative or consume one or more components from the Knative project.</p><figure name="ca72" id="ca72" class="graf graf--figure graf-after--p"><div class="aspectRatioPlaceholder is-locked" style="max-width: 700px; max-height: 440px;"><div class="aspectRatioPlaceholder-fill" style="padding-bottom: 62.8%;"></div><img class="graf-image" data-image-id="0*v-wKOVy6dsJdbABA" data-width="1600" data-height="1005" data-is-featured="true" src="https://cdn-images-1.medium.com/max/800/0*v-wKOVy6dsJdbABA"></div><figcaption class="imageCaption">Knative audience</figcaption></figure><blockquote name="15c2" id="15c2" class="graf graf--blockquote graf-after--figure">Knative helps developers build, deploy, and manage modern serverless workloads on Kubernetes.</blockquote><p name="b4e2" id="b4e2" class="graf graf--p graf-after--blockquote">It provides a set of building blocks that enable modern, source-centric and container-based development workloads on Kubernetes:</p><ul class="postList"><li name="5f0a" id="5f0a" class="graf graf--li graf-after--p"><a href="https://github.com/knative/build" data-href="https://github.com/knative/build" class="markup--anchor markup--li-anchor" rel="noopener" target="_blank">Build</a> — Source-to-container build orchestration</li><li name="c06f" id="c06f" class="graf graf--li graf-after--li"><a href="https://github.com/knative/eventing" data-href="https://github.com/knative/eventing" class="markup--anchor markup--li-anchor" rel="noopener" target="_blank">Eventing</a> — Management and delivery of events</li><li name="b148" id="b148" class="graf graf--li graf-after--li"><a href="https://github.com/knative/serving" data-href="https://github.com/knative/serving" class="markup--anchor markup--li-anchor" rel="noopener" target="_blank">Serving</a> — Request-driven compute that can scale to zero</li></ul><p name="abed" id="abed" class="graf graf--p graf-after--li">Knative documentation provides instructions on <a href="../../install/README.md" data-href="../../install/README.md" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">how to install</a> it on hosted Kubernetes offering like <a href="../../install/Knative-with-GKE.md" data-href="../../install/Knative-with-GKE.md" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">Google Cloud Platform</a> or <a href="../../install/Knative-with-IKS.md" data-href="../../install/Knative-with-IKS.md" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">IBM</a>, and on-prem Kubernetes installations, like the one offered by <a href="../../install/Knative-with-PKS.md" data-href="../../install/Knative-with-PKS.md" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">Pivotal</a>. Finally, Knative repository also includes <a href="../../install/getting-started-knative-app.md" data-href="../../install/getting-started-knative-app.md" class="markup--anchor markup--p-anchor" rel="noopener" target="_blank">samples and how-to instructions</a> to get you started developing on Kubernetes.</p><h3 name="0113" id="0113" class="graf graf--h3 graf-after--p">Knative Overview</h3><p name="e295" id="e295" class="graf graf--p graf-after--h3">Knative is based on the premise of clear separation of concerns. It allows developers and operators to reason about the workload development, deployment, and management by defining primitive objects in a form of Custom Resource Definitions (CRDs) which extend on the object model found in Kubernetes.</p><figure name="de3e" id="de3e" class="graf graf--figure graf-after--p"><div class="aspectRatioPlaceholder is-locked" style="max-width: 700px; max-height: 431px;"><div class="aspectRatioPlaceholder-fill" style="padding-bottom: 61.6%;"></div><img class="graf-image" data-image-id="0*hfyRGyNWNFycw5bx" data-width="740" data-height="456" src="https://cdn-images-1.medium.com/max/800/0*hfyRGyNWNFycw5bx"></div><figcaption class="imageCaption">Knative defines primitives with clear separation of concerns</figcaption></figure><ul class="postList"><li name="2cb6" id="2cb6" class="graf graf--li graf-after--figure"><strong class="markup--strong markup--li-strong">Configuration</strong> — is the desired state for your service, both code and configuration</li><li name="5be3" id="5be3" class="graf graf--li graf-after--li"><strong class="markup--strong markup--li-strong">Revision</strong> — represents an immutable point-in-time snapshot of your code and configuration</li><li name="8193" id="8193" class="graf graf--li graf-after--li"><strong class="markup--strong markup--li-strong">Route</strong> — assigns traffic to a revision or revisions of your service</li><li name="269b" id="269b" class="graf graf--li graf-after--li"><strong class="markup--strong markup--li-strong">Service </strong>— is the combined lite version of all the above objects to enable simple use cases</li></ul><p name="6ed0" id="6ed0" class="graf graf--p graf-after--li">In addition to these objects, Knative also defines principle objects for eventing… you know, because serverless. Knative decouples event producers and consumers and implements CNCF CloudEvents (v0.1) to streamline event processing.</p><figure name="6396" id="6396" class="graf graf--figure graf-after--p"><div class="aspectRatioPlaceholder is-locked" style="max-width: 700px; max-height: 559px;"><div class="aspectRatioPlaceholder-fill" style="padding-bottom: 79.80000000000001%;"></div><img class="graf-image" data-image-id="0*3jjrwXWgze2pPhnm" data-width="762" data-height="608" src="https://cdn-images-1.medium.com/max/800/0*3jjrwXWgze2pPhnm"></div><figcaption class="imageCaption">Knative eventing constructs</figcaption></figure><ul class="postList"><li name="dc26" id="dc26" class="graf graf--li graf-after--figure"><strong class="markup--strong markup--li-strong">Event Sources</strong> — represents the producer of events (e.g. GitHub)</li><li name="4cc7" id="4cc7" class="graf graf--li graf-after--li"><strong class="markup--strong markup--li-strong">Event Types</strong> — describes the types of events supported by the different event sources (e.g. Webhook for the above mentioned GitHub source)</li><li name="dc2c" id="dc2c" class="graf graf--li graf-after--li"><strong class="markup--strong markup--li-strong">Event Consumers</strong> — represents the target of your action (i.e. any route defined by Knative)</li><li name="2882" id="2882" class="graf graf--li graf-after--li"><strong class="markup--strong markup--li-strong">Event Feeds</strong> — is the binding or configuration connecting the event types to actions</li></ul><p name="638e" id="638e" class="graf graf--p graf-after--li">The functional implementation of the Knative object model means that Knative is both easy to start with, but capable enough to address more advanced use cases as the complexity of your solutions increases.</p><h3 name="e2f4" id="e2f4" class="graf graf--h3 graf-after--p">Summary</h3><p name="5231" id="5231" class="graf graf--p graf-after--h3">I hope this introduction gave you an understanding of the value of Knative. And how the Knative objects streamline development on Kubernetes, regardless if you work on applications or functions.</p><p name="ecf2" id="ecf2" class="graf graf--p graf-after--p graf--trailing">Over the next few weeks I will be covering each one of the key Knative usage patterns (image push, blue/green deployment model, source to URL, etc). In each post, I will also provide a sample code to illustrate that pattern and allow you to reproduce them on Knative. I’m super excited to share Knative with you, and I hope you come back to find out more.</p></div></div></section>
</section>
<footer><p>By <a href="https://medium.com/@mchmarny_google" class="p-author h-card">Mark Chmarny</a> on <a href="https://medium.com/p/4e6d8604972"><time class="dt-published" datetime="2018-11-14T02:20:46.348Z">November 14, 2018</time></a>.</p><p><a href="https://medium.com/@mchmarny_google/build-deploy-manage-modern-serverless-workloads-using-knative-on-kubernetes-4e6d8604972" class="p-canonical">Canonical link</a></p><p>Exported from <a href="https://medium.com">Medium</a> on January 8, 2019.</p></footer></article></body></html>
6 changes: 6 additions & 0 deletions blog/articles/_index.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
title: "Knative articles"
linkTitle: "Articles"
weight: 30
---

Loading

0 comments on commit 3c04f86

Please sign in to comment.