riff is for functions

riff is for functions

  • Docs
  • Blog
  • GitHub
  • Slack

›Knative Runtime

Version (v0.4.x)

  • v0.6.x (snapshot)
  • v0.5.x
  • v0.3.x

Getting Started

  • Pick your environment
  • GKE
  • Minikube
  • Docker for Mac
  • Docker for Windows

Runtimes

  • Core
  • Knative

Function Invokers

  • Java
  • Node.js
  • Command

CLI Reference

  • riff
  • riff doctor
  • riff completion
  • Credential

    • riff credential
    • riff credential apply
    • riff credential delete
    • riff credential list

    Build

    • riff function
    • riff function create
    • riff function delete
    • riff function list
    • riff function status
    • riff function tail
    • riff application
    • riff application create
    • riff application delete
    • riff application list
    • riff application status
    • riff application tail
    • riff container
    • riff container create
    • riff container delete
    • riff container list
    • riff container status

    Core Runtime

    • riff core
    • riff core deployer
    • riff core deployer create
    • riff core deployer delete
    • riff core deployer list
    • riff core deployer status
    • riff core deployer tail

    Knative Runtime

    • riff knative
    • riff knative adapter
    • riff knative adapter create
    • riff knative adapter delete
    • riff knative adapter list
    • riff knative adapter status
    • riff knative deployer
    • riff knative deployer create
    • riff knative deployer delete
    • riff knative deployer list
    • riff knative deployer status
    • riff knative deployer tail
Edit

riff knative deployer

riff knative deployer

deployers map HTTP requests to a workload

Synopsis

Deployers can be created for a build reference or image. Build based deployers continuously watch for the latest built image and will deploy new images. If the underlying build resource is deleted, the deployer will continue to run, but will no longer self update. Image based deployers must be manually updated to trigger roll out of an updated image.

Users wishing to perform checks on built images before deploying them can provide their own external process to watch the build resource for new images and only update the deployer image once those checks pass.

The hostname to access the deployer is available in the deployer listing.

Options

  -h, --help   help for deployer

Options inherited from parent commands

      --config file        config file (default is $HOME/.riff.yaml)
      --kube-config file   kubectl config file (default is $HOME/.kube/config)
      --no-color           disable color output in terminals

SEE ALSO

  • riff knative - Knative runtime for riff workloads
  • riff knative deployer create - create a deployer to map HTTP requests to a workload
  • riff knative deployer delete - delete deployer(s)
  • riff knative deployer list - table listing of deployers
  • riff knative deployer status - show knative deployer status
  • riff knative deployer tail - watch deployer logs
← riff knative adapter statusriff knative deployer create →
  • riff knative deployer
    • Synopsis
    • Options
    • Options inherited from parent commands
    • SEE ALSO
riff is for functions
Docs
Versions
Community
BlogGitHubSlackKnativeTwitter
More
Privacy PolicyTerms of UseCode of Conduct
Deployed by Netlify
Copyright © 2021 VMware, Inc