upgrade to latest dependencies (#2008)

bumping knative.dev/eventing c9821a9...7ea8857:
  > 7ea8857 [main] Upgrade to latest dependencies (# 8647)
  > db313c1 feat: webhook validates new config-observability (# 8633)
  > 4e3838c fix: containersource template labels are correctly set on deployment (# 8634)
  > aef77d7 Add option to ApiServerSource to skip permissions check (# 8615)
  > 37dd673 Instrument adapater with otel, cleanup OpenCensus references (# 8640)
bumping golang.org/x/time 2c6c5a2...1616a7f:
  > 1616a7f rate: skip time.Now call in Sometimes.Do unless necessary
  > 0c50ed8 all: upgrade go directive to at least 1.23.0 [generated]
  > 66520f6 rate: simplify function advance only returns new Tokens to caller
bumping knative.dev/serving bf962e6...5765200:
  > 5765200 upgrade to latest dependencies (# 15969)
  > f1f4f69 Update net-kourier nightly (# 15972)
  > 2af2419 Update net-istio nightly (# 15971)

Signed-off-by: Knative Automation <automation@knative.team>

.codecov.yaml

@@ -1,5 +1,24 @@
+coverage:
+  # Commit status https://docs.codecov.io/docs/commit-status are used
+  # to block PR based on coverage threshold.
+  status:
+    project:
+      default:
+        # Temporarily lowering below 80% to unblock PRs
+        target: 75
+        threshold: 5%
+    patch:
+      # Disable the coverage threshold of the patch, so that PRs are
+      # only failing because of overall project coverage threshold.
+      # See https://docs.codecov.io/docs/commit-status#disabling-a-status.
+      default: false
+comment:
+  # Update existing comment or create new if deleted.
+  behavior: default
 ignore:
   - "**/zz_generated*.go" # Ignore generated files.
+  - "**/*.pb.go" # Ignore proto-generated files.
+  - "hack"
   - "pkg/client"
+  - "test"
   - "third_party"
-  - "vendor"

.github/ISSUE_TEMPLATE/knative48h.md

@@ -0,0 +1,50 @@
+---
+name: 48h Knative Mini-Project
+about: This template is for creating a mini-project issue for the 48h Knative event. It will serve as a guide for potential participants to understand and choose projects they are interested in.
+title: "[48h Knative] "
+labels: knative48h
+assignees: ''
+---
+
+👋 Hello awesome contributor!
+
+Are you excited about Knative and open-source development? You're in the right place! This is a mini-project for the upcoming 48h Knative event—a 48-hour hackathon designed to boost contributions to the Knative Client project. For more details, check out [Issue #1842](https://github.com/knative/client/issues/1842).
+
+## 🎯 Project Description
+<!-- Briefly describe the project. -->
+
+## 🌟 Benefits
+<!-- Explain why this project is important. -->
+
+## 🛠 Difficulty Level
+<!-- Easy, Intermediate, Challenging -->
+
+## 👥 Recommended Team Size
+<!-- Suggested number of contributors for this project. -->
+
+## 🎉 Expected Outcome
+<!-- What should be accomplished by the end of the hackathon. -->
+
+## 🤝 Mentor
+<!-- Who will be available for guidance and questions? -->
+
+## 🎥 5-Minute Video Pitch
+<!-- Link to a brief video explaining the project. -->
+
+## 📝 Additional Information
+<!-- Any prerequisites or other information. -->
+
+## 🌐 Entrypoints
+<!-- Links to relevant source code or documentation. -->
+
+---
+
+### 📋 Organizer Checklist
+
+
+- [ ] Added to Project Board
+- [ ] Proposal Reviewed
+- [ ] Assigned a Mentor
+- [ ] Expected Outcome define
+
+

.github/pull-request-template.md

@@ -16,21 +16,15 @@
 <!-- Please add the corresponding issue number which this pull request is about to fix -->
 Fixes #
 
-<!--
-Please add an entry to CHANGELOG.adoc file, too, as part of your Pull Request.
+**Release Note**
 
-In the following cases, add a short description of PR to the unreleased section in CHANGELOG.adoc:
+<!-- Enter your extended release note in the below block. If the PR requires
+additional action from users switching to the new release, include the string
+"action required". If no release note is required, write "NONE". -->
 
-- 🎁 New feature
-- 🐛 Bug fix
-- ✨ Feature Update
-- 🐣 Refactoring
-- 🗑️ Remove feature or internal logic
+```release-note
 
-See other entries in CHANGELOG.adoc as an example for how to add the entry, including a reference to the corresponding issue/PR
-
-PLEASE DON'T ADD THAT LINE HERE IN THE PULL-REQUEST DESCRIPTION BUT DIRECTLY IN CHANGELOG.ADOC AND ADD CHANGELOG.ADOC AS PART OF YOUR PULL-REQUEST.
--->
+```
 
 <!--
 To automatically lint go code in this pull request uncomment the line below. You get feedback as comments on your pull request then -->

.github/workflows/knative-boilerplate.yaml

@@ -1,96 +0,0 @@
-# Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
-
-name: Boilerplate
-
-on:
-  pull_request:
-    branches: [ 'main', 'master', 'release-*' ]
-
-jobs:
-
-  check:
-    name: Boilerplate Check
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false # Keep running if one leg fails.
-      matrix:
-        extension:
-        - go
-        - sh
-
-        # Map between extension and human-readable name.
-        include:
-        - extension: go
-          language: Go
-        - extension: sh
-          language: Bash
-
-    steps:
-
-      - name: Set up Go 1.17.x
-        uses: actions/setup-go@v2
-        with:
-          go-version: 1.17.x
-        id: go
-
-      - name: Check out code
-        uses: actions/checkout@v2
-
-      - name: Install Tools
-        run: |
-          TEMP_PATH="$(mktemp -d)"
-          cd $TEMP_PATH
-
-          echo '::group::🐶 Installing reviewdog ... https://github.com/reviewdog/reviewdog'
-          curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b "${TEMP_PATH}" 2>&1
-          echo '::endgroup::'
-
-          echo '::group:: Installing boilerplate-check ... https://github.com/mattmoor/boilerplate-check'
-          go install github.com/mattmoor/boilerplate-check/cmd/boilerplate-check@latest
-          echo '::endgroup::'
-
-          echo "${TEMP_PATH}" >> $GITHUB_PATH
-
-      - id: boilerplate_txt
-        uses: andstor/file-existence-action@v1
-        with:
-          files: ./hack/boilerplate/boilerplate.${{ matrix.extension }}.txt
-      - name: ${{ matrix.language }} license boilerplate
-        shell: bash
-        if: ${{ steps.boilerplate_txt.outputs.files_exists == 'true' }}
-        env:
-          REVIEWDOG_GITHUB_API_TOKEN: ${{ github.token }}
-        run: |
-          set -e
-          cd "${GITHUB_WORKSPACE}" || exit 1
-
-          echo '::group:: Running github.com/mattmoor/boilerplate-check for ${{ matrix.language }} with reviewdog 🐶 ...'
-          # Don't fail because of boilerplate-check
-          set +o pipefail
-          boilerplate-check check \
-            --boilerplate ./hack/boilerplate/boilerplate.${{ matrix.extension }}.txt \
-            --file-extension ${{ matrix.extension }} \
-            --exclude "(vendor|third_party)/" |
-          reviewdog -efm="%A%f:%l: %m" \
-                -efm="%C%.%#" \
-                -name="${{ matrix.language }} headers" \
-                -reporter="github-pr-check" \
-                -filter-mode="diff_context" \
-                -fail-on-error="true" \
-                -level="error"
-          echo '::endgroup::'

.github/workflows/knative-donotsubmit.yaml

@@ -1,61 +0,0 @@
-# Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
-
-name: Do Not Submit
-
-on:
-  pull_request:
-    branches: [ 'main', 'master', 'release-*' ]
-
-jobs:
-
-  donotsubmit:
-    name: Do Not Submit
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Check out code
-        uses: actions/checkout@v2
-
-      - name: Do Not Submit
-        shell: bash
-        env:
-          REVIEWDOG_GITHUB_API_TOKEN: ${{ github.token }}
-        run: |
-          set -e
-          cd "${GITHUB_WORKSPACE}" || exit 1
-
-          TEMP_PATH="$(mktemp -d)"
-          PATH="${TEMP_PATH}:$PATH"
-
-          echo '::group::🐶 Installing reviewdog ... https://github.com/reviewdog/reviewdog'
-          curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b "${TEMP_PATH}" 2>&1
-          echo '::endgroup::'
-
-          echo '::group:: Running DO NOT SUBMIT with reviewdog 🐶 ...'
-          # Don't fail because of grep
-          set +o pipefail
-          find . -type f -not -path './vendor/*' -not -path './third_party/*' -not -path './.git/*' -not -path './.github/workflows/*' |
-          xargs grep -n "DO NOT SUBMIT" |
-          reviewdog -efm="%f:%l:%m" \
-                -name="DO NOT SUBMIT" \
-                -reporter="github-pr-check" \
-                -filter-mode="added" \
-                -fail-on-error="true" \
-                -level="error"
-
-          echo '::endgroup::'

.github/workflows/knative-go-build.yaml

@@ -1,65 +1,14 @@
 # Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
+# SPDX-License-Identifier: Apache-2.0
 
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
+# This file is automagically synced here from github.com/knative-extensions/knobots
 
 name: Build
 
 on:
   pull_request:
-    branches: [ 'main', 'master', 'release-*' ]
+    branches: [ 'main', 'release-*' ]
 
 jobs:
-
   build:
-    name: Build
-    strategy:
-      matrix:
-        go-version: [1.17.x]
-        platform: [ubuntu-latest]
-
-    runs-on: ${{ matrix.platform }}
-
-    steps:
-
-      - name: Set up Go ${{ matrix.go-version }}
-        uses: actions/setup-go@v2
-        with:
-          go-version: ${{ matrix.go-version }}
-        id: go
-
-      - name: Check out code
-        uses: actions/checkout@v2
-
-      - id: go_mod
-        uses: andstor/file-existence-action@v1
-        with:
-          files: go.mod
-
-      - name: Build
-        if: ${{ steps.go_mod.outputs.files_exists == 'true' }}
-        run: |
-          tags="$(grep -I  -r '// +build' . | \
-                grep -v '^./vendor/' | \
-                grep -v '^./hack/' | \
-                grep -v '^./third_party' | \
-                cut -f3 -d' ' | \
-                tr ',' '\n' | \
-                sort | uniq | \
-                grep -v '^!' | \
-                tr '\n' ' ')"
-
-          echo "Building with tags: ${tags}"
-          go test -vet=off -tags "${tags}" -exec echo ./...
+    uses: knative/actions/.github/workflows/reusable-go-build.yaml@main

.github/workflows/knative-go-test.yaml

@@ -1,81 +1,19 @@
-# Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
+# Copyright 2022 The Knative Authors.
+# SPDX-License-Identifier: Apache-2.0
 
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
+# This file is automagically synced here from github.com/knative-extensions/knobots
 
 name: Test
 
 on:
-
   push:
-    branches: [ 'main', 'master' ]
+    branches: [ 'main', 'release-*' ]
 
   pull_request:
-    branches: [ 'main', 'master', 'release-*' ]
+    branches: [ 'main', 'release-*' ]
 
 jobs:
-
   test:
-    name: Unit Tests
-    strategy:
-      matrix:
-        go-version: [1.17.x]
-        platform: [ubuntu-latest]
-
-    runs-on: ${{ matrix.platform }}
-
-    steps:
-
-      - name: Set up Go ${{ matrix.go-version }}
-        uses: actions/setup-go@v2
-        with:
-          go-version: ${{ matrix.go-version }}
-        id: go
-
-      - name: Check out code
-        uses: actions/checkout@v2
-        with:
-          fetch-depth: 0
-
-      - name: Merge upstream
-        if: github.event_name == 'pull_request'
-        run: |
-          if ! git config user.name > /dev/null; then
-            git config user.name "John Doe"
-          fi
-          if ! git config user.email > /dev/null; then
-            git config user.email "johndoe@localhost"
-          fi
-          git remote add upstream https://github.com/${{ github.repository }}.git
-          git fetch upstream ${{ github.base_ref }}
-          git pull --no-rebase --no-commit upstream ${{ github.base_ref }}
-        shell: bash
-
-      - name: Check for .codecov.yaml
-        id: codecov-enabled
-        uses: andstor/file-existence-action@v1
-        with:
-          files: .codecov.yaml
-
-      - if: steps.codecov-enabled.outputs.files_exists == 'true'
-        name: Produce Go Coverage
-        run: echo 'COVER_OPTS=-coverprofile=coverage.txt -covermode=atomic' >> $GITHUB_ENV
-
-      - name: Test
-        run: go test -race $COVER_OPTS ./...
-
-      - if: steps.codecov-enabled.outputs.files_exists == 'true'
-        name: Codecov
-        uses: codecov/codecov-action@v1
+    uses: knative/actions/.github/workflows/reusable-go-test.yaml@main
+    secrets:
+      CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/knative-releasability.yaml

@@ -1,163 +0,0 @@
-# Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
-
-name: 'Releasability'
-
-on:
-  schedule:
-    - cron: '0 1 * * 1-5' # 6am Pacific, weekdays.
-
-  workflow_dispatch:      # Manual trigger.
-    inputs:
-      releaseFamily:
-        description: 'Release? (vX.Y)'
-      moduleReleaseFamily:
-        description: 'Module Release? (vX.Y)'
-      slackChannel:
-        description: 'Slack Channel? (release-#)'
-
-jobs:
-  releasability:
-    name: Releasability
-    runs-on: 'ubuntu-latest'
-
-    env:
-      #########################################
-      #   Update this section each release.   #
-      RELEASE: 'v1.3'
-      MODULE_RELEASE: 'v0.30'
-      SLACK_CHANNEL: 'release-1dot3'
-      #########################################
-
-    steps:
-      - name: Defaults
-        run: |
-          # If manual trigger sent releaseFamily, moduleReleaseFamily and slackChannel, then override them
-          if [[ "${{ github.event.inputs.releaseFamily }}" != "" ]]; then
-            echo "RELEASE=${{ github.event.inputs.releaseFamily }}" >> $GITHUB_ENV
-          fi
-          if [[ "${{ github.event.inputs.moduleReleaseFamily }}" != "" ]]; then
-            echo "MODULE_RELEASE=${{ github.event.inputs.moduleReleaseFamily }}" >> $GITHUB_ENV
-          fi
-          if [[ "${{ github.event.inputs.slackChannel }}" != "" ]]; then
-            echo "SLACK_CHANNEL=${{ github.event.inputs.slackChannel }}" >> $GITHUB_ENV
-          fi
-          if [[ "${{ secrets.SLACK_WEBHOOK }}" != "" ]]; then
-            echo "SLACK_WEBHOOK=exists" >> $GITHUB_ENV
-          fi
-
-      - name: Set up Go
-        uses: actions/setup-go@v2
-        with:
-          go-version: 1.17.x
-
-      - name: Install Dependencies
-        run: go install knative.dev/test-infra/buoy@main
-
-      - name: Check out code
-        uses: actions/checkout@v2
-
-      - name: Exists
-        id: exists
-        run: |
-          EXISTS=0
-          buoy exists go.mod --release ${RELEASE} --module-release ${MODULE_RELEASE} --verbose || EXISTS=$?
-          if [[ "$EXISTS" -eq "0" ]]; then
-            EXISTS=true
-          else
-            EXISTS=false
-          fi
-          echo ::set-output name=release-branch::${EXISTS}
-
-      - name: Check
-        if: steps.exists.outputs.release-branch == 'false'
-        run: |
-          # The following pushes the stdout of buoy into $CHECK_MESSAGE
-          CHECK=0
-          echo 'CHECK_MESSAGE<<EOF' >> $GITHUB_ENV
-          buoy check go.mod --release ${RELEASE} --module-release ${MODULE_RELEASE} --domain knative.dev --verbose >> $GITHUB_ENV 2>&1 || CHECK=$?
-          echo 'EOF' >> $GITHUB_ENV
-
-          # We just captured the return code of the buoy call, test it to see
-          # if we should continue validating. The next steps short circuit if
-          # we already know we are not ready for a release.
-          if [[ "$CHECK" -eq "0"  ]]; then
-            echo 'current=true' >> $GITHUB_ENV
-          else
-            echo 'current=false' >> $GITHUB_ENV
-          fi
-
-      - name: Upgrade
-        if: steps.exists.outputs.release-branch == 'false' && env.current == 'true'
-        run: |
-          # if update deps returns un-successful, then mark current to false.
-          if ! ./hack/update-deps.sh --release ${RELEASE} --module-release ${MODULE_RELEASE} --upgrade; then
-            echo "VERIFY_MESSAGE=Unable to update deps for ${{ github.repository }}." >> $GITHUB_ENV
-            echo 'current=false' >> $GITHUB_ENV
-          fi
-
-      - name: Verify
-        if: steps.exists.outputs.release-branch == 'false' && env.current == 'true'
-        run: |
-          # If we don't run `git status` before the "git diff-index" it seems
-          # to list every file that's been touched by codegen.
-          git status
-
-          CHANGED="$(git diff-index --name-only HEAD --)"
-
-          # If we see no changes after the upgrade, then we are up to date.
-          if [[ "$CHANGED" == "" ]]; then
-              echo "VERIFY_MESSAGE=${{ github.repository }} up to date." >> $GITHUB_ENV
-          else
-              echo "VERIFY_MESSAGE=${{ github.repository }} is out of date." >> $GITHUB_ENV
-              echo "The following files are changed: $CHANGED"
-              echo 'current=false' >> $GITHUB_ENV
-          fi
-
-      - name: Status GO
-        if: steps.exists.outputs.release-branch == 'false' && env.current == 'true'
-        run: |
-          echo 'SLACK_COLOR=#098e00' >> $GITHUB_ENV
-          echo 'SLACK_TITLE=Releasability for ${{ github.repository }} @ ${{ env.RELEASE }} is GO!' >> $GITHUB_ENV
-
-      - name: Status NO-GO
-        if: steps.exists.outputs.release-branch == 'false' && env.current == 'false'
-        run: |
-          echo 'SLACK_COLOR=#8E1600' >> $GITHUB_ENV
-          echo 'SLACK_TITLE=Releasability for ${{ github.repository }} @ ${{ env.RELEASE }} is NO-GO!' >> $GITHUB_ENV
-
-      - name: Post status to Slack
-        # Note: using env.SLACK_WEBHOOK here because secrets are not allowed in the if block.
-        if: env.SLACK_WEBHOOK != '' && steps.exists.outputs.release-branch == 'false'
-        uses: rtCamp/action-slack-notify@v2.1.0
-        env:
-          SLACK_ICON: http://github.com/knative.png?size=48
-          SLACK_USERNAME: github-actions
-          SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}
-          MSG_MINIMAL: 'true'
-          SLACK_MESSAGE: |
-            ${{ env.CHECK_MESSAGE }}
-            ${{ env.VERIFY_MESSAGE }}
-            For detailed logs: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}
-
-      - name: Fail if NO-GO
-        if: steps.exists.outputs.release-branch == 'false' && env.current == 'false'
-        run: |
-          # When we have figured out that things are NO-GO, we intentionally fail the job
-          # so that the status badge shows up red and we can use the badges to create a
-          # releasability dashboard for all of the repos.
-          exit 1

.github/workflows/knative-release-notes.yaml

@@ -1,104 +0,0 @@
-# Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
-
-name: 'Release Notes'
-
-on:
-  workflow_dispatch:
-    inputs:
-      branch:
-        description: 'Branch'
-        required: true
-        default: 'main'
-      start-rev:
-        description: 'Start Tag (defaults to merge-base(branch, prev-branch))'
-      end-rev:
-        description: 'End Tag (defaults to HEAD of the target branch)'
-
-jobs:
-  release-notes:
-    name: Release Notes
-    runs-on: 'ubuntu-latest'
-
-    env:
-      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-    steps:
-      - name: Set up Go
-        uses: actions/setup-go@v2
-        with:
-          go-version: 1.17.x
-
-      - name: Install Dependencies
-        # https://github.com/kubernetes/release/tree/master/cmd/release-notes
-        run: go install k8s.io/release/cmd/release-notes@latest
-
-      - name: Check out code
-        uses: actions/checkout@v2
-        with:
-          # fetch-depth of 0 indicates all history for all branches and tags.
-          fetch-depth: 0
-
-      - name: Generate Notes
-        run: |
-          set -x
-          # The release-notes tool access ENV vars as options
-          # https://github.com/kubernetes/release/tree/master/cmd/release-notes#options
-
-          export ORG=$(echo '${{ github.repository }}' | awk -F '/' '{print $1}')
-          export REPO=$(echo '${{ github.repository }}' | awk -F '/' '{print $2}')
-          export BRANCH="${{ github.event.inputs.branch }}"
-
-          export START_REV=${{ github.event.inputs.start-rev }}
-          export END_REV=${{ github.event.inputs.end-rev }}
-
-          if [[ -z "$END_REV" ]]; then
-            END_REV="origin/$BRANCH"
-          fi
-
-          # If start rev isn't set find the merge base of
-          # the target branch and the previous branch
-          if [[ -z "$START_REV" ]]; then
-            BRANCHES=$(mktemp)
-            # List of branches sorted by semver descending
-            git branch -r -l "origin/release-[0-9]*\.[0-9]*" | sed 's/ //g' | sort -Vr > "$BRANCHES"
-
-            if [[ "$BRANCH" == "main" ]]; then
-              LAST_BRANCH="$(head -n1 "$BRANCHES")"
-            else
-              # use grep magic to find the next branch
-              # '-A 1' - prints the line after the match which we can parse
-              LAST_BRANCH="$(grep -A 1 "$BRANCH" "$BRANCHES" | tail -n1)"
-            fi
-
-            export START_SHA=$(git merge-base $LAST_BRANCH origin/$BRANCH)
-          fi
-
-          release-notes \
-           --required-author="" \
-           --output=release-notes.md \
-           --repo-path="$PWD" \
-
-      - name: Display Notes
-        run: |
-          cat release-notes.md
-
-      - name: Archive Release Notes
-        uses: actions/upload-artifact@v2
-        with:
-          name: release-notes.md
-          path: release-notes.md

.github/workflows/knative-security.yaml

@@ -1,56 +1,17 @@
 # Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
+# SPDX-License-Identifier: Apache-2.0
 
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
+# This file is automagically synced here from github.com/knative-extensions/knobots
 
 name: 'Security'
 
 on:
   push:
-    branches: [ 'main', 'master', 'release-*' ]
+    branches: [ 'main', 'release-*' ]
 
   pull_request:
-    branches: [ 'main', 'master', 'release-*' ]
+    branches: [ 'main', 'release-*' ]
 
 jobs:
   analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
-
-    # Initializes the CodeQL tools for scanning.
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: go
-
-    - name: Autobuild
-      uses: github/codeql-action/autobuild@v1
-
-    - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v1
-
-    - name: Find Unicode Control Characters
-      uses: pierdipi/unicode-control-characters-action@v0.1.1
-      with:
-        args: -d .
-
+    uses: knative/actions/.github/workflows/reusable-security.yaml@main

.github/workflows/knative-stale.yaml

@@ -1,20 +1,7 @@
 # Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
+# SPDX-License-Identifier: Apache-2.0
 
+# This file is automagically synced here from github.com/knative-extensions/knobots
 name: 'Close stale'
 
 on:
@@ -22,28 +9,6 @@ on:
   - cron: '0 1 * * *'
 
 jobs:
+
   stale:
-    runs-on: 'ubuntu-latest'
-    steps:
-    - uses: 'actions/stale@v3'
-      with:
-        repo-token: '${{ secrets.GITHUB_TOKEN }}' # No need to setup
-
-        stale-issue-message: |-
-          This issue is stale because it has been open for 90 days with no
-          activity. It will automatically close after 30 more days of
-          inactivity. Reopen the issue with `/reopen`. Mark the issue as
-          fresh by adding the comment `/remove-lifecycle stale`.
-        stale-issue-label: 'lifecycle/stale'
-        exempt-issue-labels: 'lifecycle/frozen,triage/accepted'
-
-        stale-pr-message: |-
-          This Pull Request is stale because it has been open for 90 days with
-          no activity. It will automatically close after 30 more days of
-          inactivity. Reopen with `/reopen`. Mark as fresh by adding the
-          comment `/remove-lifecycle stale`.
-        stale-pr-label: 'lifecycle/stale'
-        exempt-pr-labels: 'lifecycle/frozen'
-
-        days-before-stale: 90
-        days-before-close: 30
+    uses: knative/actions/.github/workflows/reusable-stale.yaml@main

.github/workflows/knative-style.yaml

@@ -1,264 +1,15 @@
 # Copyright 2020 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
+# SPDX-License-Identifier: Apache-2.0
 
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
+# This file is automagically synced here from github.com/knative-extensions/knobots
 
 name: Code Style
 
 on:
   pull_request:
-    branches: [ 'main', 'master', 'release-*' ]
+    branches: [ 'main', 'release-*' ]
 
 jobs:
 
-  autoformat:
-    name: Auto-format and Check
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false # Keep running if one leg fails.
-      matrix:
-        tool:
-          - goimports
-          - gofmt
-
-        include:
-        - tool: gofmt
-          options: -s
-        - tool: goimports
-          package: golang.org/x/tools/cmd/goimports@latest
-
-    steps:
-      - name: Set up Go
-        uses: actions/setup-go@v2
-        with:
-          go-version: 1.17.x
-        id: go
-
-      - name: Check out code
-        uses: actions/checkout@v2
-
-      - name: Install Dependencies
-        if: ${{ matrix.package != '' }}
-        run: |
-          cd $(mktemp -d)
-          go install ${{ matrix.package }}
-
-      - name: ${{ matrix.tool }} ${{ matrix.options }}
-        shell: bash
-        run: >
-          ${{ matrix.tool }} ${{ matrix.options }} -w
-          $(find .
-          -path './vendor' -prune
-          -o -path './third_party' -prune
-          -o -name '*.pb.go' -prune
-          -o -name 'wire_gen.go' -prune
-          -o -type f -name '*.go' -print)
-
-      - name: Verify ${{ matrix.tool }}
-        shell: bash
-        run: |
-          # From: https://backreference.org/2009/12/23/how-to-match-newlines-in-sed/
-          # This is to leverage this workaround:
-          # https://github.com/actions/toolkit/issues/193#issuecomment-605394935
-          function urlencode() {
-            sed ':begin;$!N;s/\n/%0A/;tbegin'
-          }
-          if [[ $(git diff-index --name-only HEAD --) ]]; then
-              for x in $(git diff-index --name-only HEAD --); do
-                echo "::error file=$x::Please run ${{ matrix.tool }} ${{ matrix.options }}.%0A$(git diff $x | urlencode)"
-              done
-              echo "${{ github.repository }} is out of style. Please run ${{ matrix.tool }} ${{ matrix.options }}."
-              exit 1
-          fi
-          echo "${{ github.repository }} is formatted correctly."
-
-  lint:
-    name: Lint
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Set up Go
-        uses: actions/setup-go@v2
-        with:
-          go-version: 1.17.x
-        id: go
-
-      - name: Check out code
-        uses: actions/checkout@v2
-
-      - id: golangci_configuration
-        uses: andstor/file-existence-action@v1
-        with:
-          files: .golangci.yaml
-      - name: Go Lint
-        if: steps.golangci_configuration.outputs.files_exists == 'true'
-        uses: golangci/golangci-lint-action@v2
-        with:
-          version: v1.43
-
-      - name: Install Tools
-        if: ${{ always() }}
-        env:
-          WOKE_VERSION: v0.13.0
-        run: |
-          TEMP_PATH="$(mktemp -d)"
-          cd $TEMP_PATH
-
-          echo '::group::🐶 Installing reviewdog ... https://github.com/reviewdog/reviewdog'
-          curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b "${TEMP_PATH}" 2>&1
-          echo '::endgroup::'
-
-          echo '::group:: Installing misspell ... https://github.com/client9/misspell'
-          curl -sfL https://raw.githubusercontent.com/client9/misspell/master/install-misspell.sh | sh -s -- -b "${TEMP_PATH}" 2>&1
-          echo '::endgroup::'
-
-          echo '::group:: Installing woke ... https://github.com/get-woke/woke'
-          curl -sfL https://raw.githubusercontent.com/get-woke/woke/main/install.sh | sh -s -- -b "${TEMP_PATH}" "${WOKE_VERSION}" 2>&1
-          echo '::endgroup::'
-
-          echo "${TEMP_PATH}" >> $GITHUB_PATH
-
-      - name: misspell
-        shell: bash
-        if: ${{ always() }}
-        env:
-          REVIEWDOG_GITHUB_API_TOKEN: ${{ github.token }}
-        run: |
-          set -e
-          cd "${GITHUB_WORKSPACE}" || exit 1
-
-          echo '::group:: Running github.com/client9/misspell with reviewdog 🐶 ...'
-          # Don't fail because of misspell
-          set +o pipefail
-          # Exclude generated and vendored files, plus some legacy
-          # paths until we update all .gitattributes
-          git ls-files |
-          git check-attr --stdin linguist-generated | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          git check-attr --stdin linguist-vendored | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          git check-attr --stdin ignore-lint | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          grep -Ev '^(vendor/|third_party/|.git)' |
-          grep -v '\.svg$' |
-          xargs misspell -i importas -error |
-          reviewdog -efm="%f:%l:%c: %m" \
-                -name="github.com/client9/misspell" \
-                -reporter="github-pr-check" \
-                -filter-mode="added" \
-                -fail-on-error="true" \
-                -level="error"
-
-          echo '::endgroup::'
-
-      - name: trailing whitespace
-        shell: bash
-        if: ${{ always() }}
-        env:
-          REVIEWDOG_GITHUB_API_TOKEN: ${{ github.token }}
-        run: |
-          set -e
-          cd "${GITHUB_WORKSPACE}" || exit 1
-
-          echo '::group:: Flagging trailing whitespace with reviewdog 🐶 ...'
-          # Don't fail because of grep
-          set +o pipefail
-
-          # Exclude generated and vendored files, plus some legacy
-          # paths until we update all .gitattributes
-          git ls-files |
-          git check-attr --stdin linguist-generated | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          git check-attr --stdin linguist-vendored | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          git check-attr --stdin ignore-lint | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          grep -Ev '^(vendor/|third_party/|.git)' |
-          grep -v '\.svg$' |
-          xargs grep -nE " +$" |
-          reviewdog -efm="%f:%l:%m" \
-                -name="trailing whitespace" \
-                -reporter="github-pr-check" \
-                -filter-mode="added" \
-                -fail-on-error="true" \
-                -level="error"
-
-          echo '::endgroup::'
-
-      - name: EOF newline
-        shell: bash
-        if: ${{ always() }}
-        env:
-          REVIEWDOG_GITHUB_API_TOKEN: ${{ github.token }}
-        run: |
-          set -e
-          cd "${GITHUB_WORKSPACE}" || exit 1
-
-          echo '::group:: Flagging missing EOF newlines with reviewdog 🐶 ...'
-          # Don't fail because of misspell
-          set +o pipefail
-          # Lint exclude rule:
-          #  - nothing in vendor/
-          #  - nothing in third_party
-          #  - nothing in .git/
-          #  - no *.ai (Adobe Illustrator) files.
-          LINT_FILES=$(git ls-files |
-          git check-attr --stdin linguist-generated | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          git check-attr --stdin linguist-vendored | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          git check-attr --stdin ignore-lint | grep -Ev ': (set|true)$' | cut -d: -f1 |
-          grep -Ev '^(vendor/|third_party/|.git)' |
-          grep -v '\.ai$' |
-          grep -v '\.svg$')
-
-          for x in $LINT_FILES; do
-            # Based on https://stackoverflow.com/questions/34943632/linux-check-if-there-is-an-empty-line-at-the-end-of-a-file
-            if [[ -f $x && ! ( -s "$x" && -z "$(tail -c 1 $x)" ) ]]; then
-              # We add 1 to `wc -l` here because of this limitation (from the man page):
-              # Characters beyond the final <newline> character will not be included in the line count.
-              echo $x:$((1 + $(wc -l $x | tr -s ' ' | cut -d' ' -f 1))): Missing newline
-            fi
-          done |
-          reviewdog -efm="%f:%l: %m" \
-                -name="EOF Newline" \
-                -reporter="github-pr-check" \
-                -filter-mode="added" \
-                -fail-on-error="true" \
-                -level="error"
-
-          echo '::endgroup::'
-
-      # This is mostly copied from https://github.com/get-woke/woke-action-reviewdog/blob/main/entrypoint.sh
-      # since their action is not yet released under a stable version.
-      - name: Language
-        if: ${{ always() && github.event_name == 'pull_request' }}
-        shell: bash
-        env:
-          REVIEWDOG_GITHUB_API_TOKEN: ${{ github.token }}
-        run: |
-          set -e
-          cd "${GITHUB_WORKSPACE}" || exit 1
-
-          # Create a minimal .wokeignore if none already exist.
-          if [ ! -f .wokeignore ]; then
-            cat > .wokeignore <<EOF
-            vendor/*
-            third_party/*
-            *.svg
-          EOF
-          fi
-
-          echo '::group:: Running woke with reviewdog 🐶 ...'
-          woke --output simple \
-            | reviewdog -efm="%f:%l:%c: %m" \
-                -name="woke" \
-                -reporter="github-pr-check" \
-                -filter-mode="added" \
-                -fail-on-error="true" \
-                -level="error"
-          echo '::endgroup::'
+  style:
+    uses: knative/actions/.github/workflows/reusable-style.yaml@main

.github/workflows/knative-verify.yaml

@@ -12,65 +12,15 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
+# This file is automagically synced here from github.com/knative-extensions/.github
+# repo by knobots: https://github.com/knative-extensions/knobots and will be overwritten.
 
 name: Verify
 
 on:
   pull_request:
-    branches: [ 'main', 'master', 'release-*' ]
+    branches: [ 'main', 'release-*' ]
 
 jobs:
-
   verify:
-    name: Verify Deps and Codegen
-    strategy:
-      matrix:
-        go-version: [1.17.x]
-        platform: [ubuntu-latest]
-
-    runs-on: ${{ matrix.platform }}
-
-    steps:
-    - name: Set up Go ${{ matrix.go-version }}
-      uses: actions/setup-go@v2
-      with:
-        go-version: ${{ matrix.go-version }}
-      id: go
-
-    - name: Install Dependencies
-      run: |
-        go install github.com/google/ko@latest
-        go install github.com/google/go-licenses@latest
-
-    - name: Check out code
-      uses: actions/checkout@v2
-
-    - name: Update Codegen
-      shell: bash
-      run: |
-        [[ ! -f hack/update-codegen.sh ]] || ./hack/update-codegen.sh
-
-    - name: Verify
-      shell: bash
-      run: |
-        # From: https://backreference.org/2009/12/23/how-to-match-newlines-in-sed/
-        # This is to leverage this workaround:
-        # https://github.com/actions/toolkit/issues/193#issuecomment-605394935
-        function urlencode() {
-          sed ':begin;$!N;s/\n/%0A/;tbegin'
-        }
-
-        if [[ -z "$(git status --porcelain)" ]]; then
-            echo "${{ github.repository }} up to date."
-        else
-            # Print it both ways because sometimes we haven't modified the file (e.g. zz_generated),
-            # and sometimes we have (e.g. configmap checksum).
-            echo "Found diffs in: $(git diff-index --name-only HEAD --)"
-            for x in $(git diff-index --name-only HEAD --); do
-                echo "::error file=$x::Please run ./hack/update-codegen.sh.%0A$(git diff $x | urlencode)"
-            done
-            echo "${{ github.repository }} is out of date. Please run hack/update-codegen.sh"
-            exit 1
-        fi
+    uses: knative/actions/.github/workflows/reusable-verify-codegen.yaml@main

.github/workflows/knative-vulnerability.yaml

@@ -1,42 +0,0 @@
-# Copyright 2021 The Knative Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
-
-name: 'Vulnerability scan'
-
-on:
-  schedule:
-    - cron: '0 1 1,15 * *' # 6am Pacific, 1st of the month to not exceed limits (200 total for all repos).
-  workflow_dispatch: {}
-
-jobs:
-  snyk:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@master
-
-      - name: Run Snyk to check for vulnerabilities
-        uses: snyk/actions/golang@master
-        continue-on-error: true # To make sure that SARIF upload gets called
-        env:
-          SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
-        with:
-          args: --sarif-file-output=snyk.sarif
-
-      - name: Upload result to GitHub Code Scanning
-        uses: github/codeql-action/upload-sarif@v1
-        with:
-          sarif_file: snyk.sarif

.golangci.yaml

@@ -1,9 +1,7 @@
+version: "2"
 run:
-  timeout: 5m
-
   build-tags:
     - e2e
-
 linters:
   enable:
     - errorlint
@@ -13,10 +11,26 @@ linters:
     - unparam
   disable:
     - errcheck
-
-issues:
-  exclude-rules:
-    - path: test # Excludes /test, *_test.go etc.
-      linters:
-        - gosec
-        - unparam
+  exclusions:
+    generated: lax
+    presets:
+      - comments
+      - common-false-positives
+      - legacy
+      - std-error-handling
+    rules:
+      - linters:
+          - gosec
+          - unparam
+        path: test
+    paths:
+      - third_party$
+      - builtin$
+      - examples$
+formatters:
+  exclusions:
+    generated: lax
+    paths:
+      - third_party$
+      - builtin$
+      - examples$

.ko.yaml

@@ -1,3 +1,10 @@
 defaultBaseImage: gcr.io/distroless/static:nonroot
 baseImageOverrides:
   knative.dev/client/cmd/kn: docker.io/library/alpine:latest
+builds:
+  - id: knative.dev/client/cmd/kn
+    main: ./cmd/kn
+    ldflags:
+      - -X knative.dev/client/pkg/kn/commands/version.Version={{.Env.KN_BUILD_VERSION}}
+      - -X knative.dev/client/pkg/kn/commands/version.GitRevision={{.Env.KN_BUILD_GITREV}}
+      - -X 'knative.dev/client/pkg/kn/commands/version.BuildDate={{.Env.KN_BUILD_DATE}}'

CHANGELOG.adoc

@@ -11,6 +11,65 @@
 |
 | https://github.com/knative/client/pull/[#]
 ////
+## v1.5.0 (2022-05-31)
+[cols="1,10,3", options="header", width="100%"]
+|===
+| | Description | PR
+
+| 🎁
+| Add delivery options to `broker create` command
+| https://github.com/knative/client/pull/1670[#1670]
+
+| 🐛
+| Fix OCI image build
+| https://github.com/knative/client/pull/1666[#1666]
+
+| ✨
+| Mark `--inject-broker` flag as deprecated
+| https://github.com/knative/client/pull/1661[#1661]
+
+|===
+
+## v1.4.1 (2022-05-17)
+[cols="1,10,3", options="header", width="100%"]
+|===
+| | Description | PR
+
+| ✨
+| Mark `--inject-broker` flag as deprecated
+| https://github.com/knative/client/pull/1665[#1665]
+
+|===
+## v1.4.0 (2022-04-20)
+[cols="1,10,3", options="header", width="100%"]
+|===
+| | Description | PR
+
+| 🎁
+| Added --timeout flag to service create, update, apply
+| https://github.com/knative/client/pull/1643[#1643]
+
+| 🎁
+| Added --pull-policy flag to service create, update, apply
+| https://github.com/knative/client/pull/1644[#1644]
+
+| 🎁
+| Added --wait-window flag to configure error window between errors during service create
+| https://github.com/knative/client/pull/1645[#1645]
+
+| 🎁
+| Added --scale-metric flag to configure metric name
+| https://github.com/knative/client/pull/1653[#1653]
+
+| 🎁
+| Added subpath functionality to --mount flag
+| https://github.com/knative/client/pull/1655[#1655]
+
+| 🐣
+| Use `T.TempDir` to create temporary test directory
+| https://github.com/knative/client/pull/1660[#1660]
+
+|===
 ## v1.3.0 (2022-03-08)
 [cols="1,10,3", options="header", width="100%"]
 |===

CODE-OF-CONDUCT.md

@@ -1,76 +1,3 @@
-# Contributor Covenant Code of Conduct
+## Knative Community Code of Conduct
 
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of
-experience, education, socio-economic status, nationality, personal appearance,
-race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-- The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Members of the Technical Oversight Committee are responsible for clarifying the
-standards of acceptable behavior and are expected to take appropriate and fair
-corrective action in response to any instances of unacceptable behavior.
-
-TOC members have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, or to ban temporarily or permanently any
-contributor for other behaviors that they deem inappropriate, threatening,
-offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the Technical Oversight Committee at
-knative-code-of-conduct@googlegroups.com. All complaints will be reviewed and
-investigated and will result in a response that is deemed necessary and
-appropriate to the circumstances. The project team is obligated to maintain
-confidentiality with regard to the reporter of an incident. Further details of
-specific enforcement policies may be posted separately.
-
-TOC members who do not follow or enforce the Code of Conduct in good faith may
-face temporary or permanent repercussions as determined by other members of the
-project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 1.4, available at
-https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
+The [Knative Community Code of Conduct](https://github.com/knative/community/blob/main/CODE-OF-CONDUCT.md) is defined in the [Knative community repository](https://github.com/knative/community).

DEVELOPMENT.md

@@ -1,10 +1,7 @@
 # Development
 
 This doc explains how to set up a development environment so you can get started
-[contributing](https://www.knative.dev/contributing/) to `Knative Client`. Also
-take a look at:
-
-- [The pull request workflow](https://www.knative.dev/contributing/reviewing/)
+[contributing](https://www.knative.dev/contributing/) to `Knative Client`.
 
 ## Prerequisites
 
@@ -35,7 +32,7 @@ You must install these tools:
 
 ### Create a cluster
 
-1. [Set up Knative](https://knative.dev/docs/install/any-kubernetes-cluster)
+1. [Set up Knative](https://knative.dev/docs/install/)
 
 ### Checkout your fork
 
@@ -65,7 +62,7 @@ Once you've [set up your development environment](#prerequisites), let's build
 
 **Dependencies:**
 
-[go mod](https://github.com/golang/go/wiki/Modules#quick-start) is used and
+[go mod](https://go.dev/wiki/Modules) is used and
 required for dependencies.
 
 **Building:**
@@ -94,7 +91,7 @@ can be directly executed.
 
 **Testing:**
 
-Please follow the [guide](../test/README.md) here to test the `knative client`.
+Please follow the [guide](test/README.md) here to test the `knative client`.
 
 **Notes:**
 

OWNERS_ALIASES

@@ -2,215 +2,130 @@
 # Do not modify this file, instead modify peribolos/knative.yaml
 
 aliases:
-  api-core-wg-leads:
-  - dprotaso
-  autoscaling-reviewers:
-  - nader-ziada
-  - psschwei
-  - skonto
-  - taragu
-  autoscaling-wg-leads:
-  - julz
-  autoscaling-writers:
-  - julz
-  - yanweiguo
   client-reviewers:
   - itsmurugappan
   client-wg-leads:
   - dsimansk
-  - navidshaikh
-  - rhuss
   client-writers:
   - dsimansk
-  - maximilien
-  - navidshaikh
-  - rhuss
-  conformance-task-force-leads:
-  - omerbensaadon
-  - salaboy
-  conformance-writers:
-  - omerbensaadon
-  - salaboy
+  - vyasgun
   docs-reviewers:
   - nainaz
-  - omerbensaadon
-  - pmbanugo
-  - snneji
-  docs-wg-leads:
-  - csantanapr
-  - snneji
+  - skonto
   docs-writers:
-  - abrennan89
   - csantanapr
-  - psschwei
-  - snneji
+  - skonto
   eventing-reviewers:
+  - Leo6Leo
   - aslom
-  - tayarani
-  - tommyreddad
-  eventing-triage:
-  - akashrv
-  - antoineco
-  - lberk
+  - cali0707
+  - creydr
   eventing-wg-leads:
-  - devguyio
-  - lionelvillard
+  - creydr
+  - pierDipi
   eventing-writers:
-  - akashrv
+  - Leo6Leo
   - aliok
-  - antoineco
-  - devguyio
-  - lberk
+  - cali0707
+  - creydr
   - lionelvillard
   - matzew
   - pierDipi
-  - vaikas
-  knative-admin:
-  - carlisia
-  - csantanapr
-  - dprotaso
-  - evankanderson
-  - itsmurugappan
-  - julz
-  - knative-prow-releaser-robot
-  - knative-prow-robot
-  - knative-prow-updater-robot
-  - knative-test-reporter-robot
-  - kvmware
+  func-reviewers:
+  - jrangelramos
+  - nainaz
+  func-writers:
+  - gauron99
+  - jrangelramos
   - lance
-  - pmorie
-  - rhuss
-  - smoser-ibm
-  - spencerdillard
-  - thisisnotapril
-  - vaikas
-  - xtreme-sameer-vohra
-  knative-release-leads:
-  - carlisia
-  - kvmware
-  - xtreme-sameer-vohra
-  knative-robots:
+  - lkingland
+  - matejvasek
+  - matzew
+  - salaboy
+  functions-wg-leads:
+  - lkingland
+  - salaboy
+  knative-admin:
+  - aliok
+  - cardil
+  - dprotaso
+  - dsimansk
+  - evankanderson
+  - gauron99
+  - knative-automation
+  - knative-prow-releaser-robot
+  - knative-prow-robot
+  - knative-prow-updater-robot
+  - knative-test-reporter-robot
+  - matzew
+  - nrrso
+  - skonto
+  - upodroid
+  knative-release-leads:
+  - dprotaso
+  - dsimansk
+  - gauron99
+  - skonto
+  knative-robots:
+  - knative-automation
   - knative-prow-releaser-robot
   - knative-prow-robot
   - knative-prow-updater-robot
   - knative-test-reporter-robot
-  networking-reviewers:
-  - JRBANCEL
-  - ZhiminXiang
-  - andrew-su
-  - arturenault
-  - carlisia
-  - nak3
-  - shashwathi
-  - tcnghia
-  - vagababov
-  - yanweiguo
-  networking-wg-leads:
-  - ZhiminXiang
-  - nak3
-  networking-writers:
-  - JRBANCEL
-  - ZhiminXiang
-  - nak3
-  - vagababov
   operations-reviewers:
-  - Cynocracy
   - aliok
   - houshengbo
-  - jcrossley3
   - matzew
-  - maximilien
-  - trshafer
   operations-wg-leads:
   - houshengbo
   operations-writers:
-  - Cynocracy
   - aliok
   - houshengbo
-  - jcrossley3
   - matzew
-  - maximilien
-  - trshafer
-  pkg-configmap-reviewers:
-  - dprotaso
-  - mattmoor
-  - vagababov
-  pkg-configmap-writers:
-  - dprotaso
-  - mattmoor
-  - vagababov
-  pkg-controller-reviewers:
-  - dprotaso
-  - mattmoor
-  - tcnghia
-  - vagababov
-  - whaught
-  pkg-controller-writers:
-  - dprotaso
-  - mattmoor
-  - tcnghia
-  - vagababov
+  productivity-leads:
+  - cardil
+  - upodroid
   productivity-reviewers:
-  - albertomilan
-  - efiturri
   - evankanderson
-  - gerardo-lc
-  - kvmware
   - mgencur
-  - shinigambit
   productivity-wg-leads:
-  - chizhg
+  - cardil
+  - upodroid
   productivity-writers:
   - cardil
-  - chaodaiG
-  - chizhg
-  - coryrc
-  - psschwei
+  - upodroid
   security-wg-leads:
+  - davidhadas
   - evankanderson
-  - julz
   security-writers:
+  - davidhadas
   - evankanderson
-  - julz
-  serving-observability-reviewers:
+  serving-approvers:
+  - dsimansk
   - skonto
-  - yanweiguo
-  serving-observability-writers:
-  - yanweiguo
   serving-reviewers:
-  - carlisia
-  - julz
-  - nader-ziada
-  - nealhu
-  - psschwei
   - skonto
-  - whaught
+  serving-triage:
+  - skonto
+  serving-wg-leads:
+  - dprotaso
   serving-writers:
   - dprotaso
-  - julz
-  - tcnghia
-  - vagababov
-  source-wg-leads:
-  - lionelvillard
+  - dsimansk
+  - skonto
   steering-committee:
-  - csantanapr
-  - itsmurugappan
-  - lance
-  - pmorie
-  - thisisnotapril
-  - vaikas
-  technical-oversight-committee:
+  - aliok
   - dprotaso
   - evankanderson
-  - julz
-  - rhuss
-  trademark-committee:
-  - evankanderson
-  - smoser-ibm
-  - spencerdillard
+  - matzew
+  - nrrso
   ux-wg-leads:
-  - csantanapr
-  - snneji
+  - Leo6Leo
+  - cali0707
+  - mmejia02
+  - zainabhusain227
   ux-writers:
-  - csantanapr
-  - snneji
+  - Leo6Leo
+  - cali0707
+  - mmejia02
+  - zainabhusain227

README.md

@@ -37,13 +37,14 @@ install Knative with its prerequisites.
 
 ## Documentation
 
-Start with the [user's guide](docs/README.md) to learn more. You can read about
+Refer to the [user's guide](https://knative.dev/docs/client/) to learn more. You can read about
 common use cases, get detailed documentation on each command, and learn how to
-extend the `kn` CLI. For more information, have a look at:
+extend the `kn` CLI.
 
-- [User guide](docs/README.md)
-  - Installation - How to install `kn` and run on your machine
-  - Examples - Use case based examples
+Following are some useful resources for getting-started using `kn` CLI:
+
+- [Installation](https://knative.dev/docs/client/install-kn/) - how to install `kn` and run on your machine
+- [Configuration](https://knative.dev/docs/client/configure-kn/) - how to customize `kn`
 - [Reference Manual](docs/cmd/kn.md) - all possible commands and options with
   usage examples
 
@@ -52,4 +53,5 @@ Additionally you can visit [knative.dev](https://knative.dev) for more examples.
 ## Developers
 
 If you are interested in contributing, see [CONTRIBUTING.md](./CONTRIBUTING.md)
-and [DEVELOPMENT.md](docs/DEVELOPMENT.md).
+and [DEVELOPMENT.md](DEVELOPMENT.md). For a list of help wanted issues in Knative,
+check out [CLOTRIBUTOR](https://clotributor.dev/search?project=knative&page=1)

SECURITY.md

@@ -0,0 +1,7 @@
+# Knative Security Policy
+
+We're extremely grateful for security researchers and users that report vulnerabilities to the Knative Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
+
+To make a report, please email the private security@knative.team list with the security details and the details expected for all Knative bug reports.
+
+See [Knative Security and Disclosure Information](https://knative.dev/docs/reference/security/) for more details.

cmd/kn/main.go

@@ -17,22 +17,16 @@ package main
 import (
 	"errors"
 	"fmt"
-	"math/rand"
 	"os"
 	"regexp"
 	"strings"
-	"time"
 
 	"github.com/spf13/cobra"
-	"knative.dev/client/pkg/kn/config"
-	"knative.dev/client/pkg/kn/plugin"
-	"knative.dev/client/pkg/kn/root"
+	"knative.dev/client/pkg/config"
+	pluginpkg "knative.dev/client/pkg/plugin"
+	"knative.dev/client/pkg/root"
 )
 
-func init() {
-	rand.Seed(time.Now().UnixNano())
-}
-
 func main() {
 	os.Exit(runWithExit(os.Args[1:]))
 }
@@ -66,7 +60,7 @@ func run(args []string) error {
 		return err
 	}
 
-	pluginManager := plugin.NewManager(config.GlobalConfig.PluginsDir(), config.GlobalConfig.LookupPluginsInPath())
+	pluginManager := pluginpkg.NewManager(config.GlobalConfig.PluginsDir(), config.GlobalConfig.LookupPluginsInPath())
 
 	// Create kn root command and all sub-commands
 	rootCmd, err := root.NewRootCommand(pluginManager.HelpTemplateFuncs())
@@ -90,13 +84,37 @@ func run(args []string) error {
 		return err
 	}
 
+	// FT: Context Sharing
+	var ctxManager *pluginpkg.ContextDataManager
+	if config.GlobalConfig.ContextSharing() {
+		ctxManager, err = pluginpkg.NewContextManager(pluginManager)
+		if err != nil {
+			return err
+		}
+
+		defer func(ctxManager *pluginpkg.ContextDataManager) {
+			if err := ctxManager.WriteCache(); err != nil {
+				println("error during write")
+			}
+		}(ctxManager)
+	}
+
 	if plugin != nil {
 		// Validate & Execute plugin
 		err = validatePlugin(rootCmd, plugin)
 		if err != nil {
 			return err
 		}
-
+		if config.GlobalConfig.ContextSharing() {
+			if pwm, ok := plugin.(pluginpkg.PluginWithManifest); ok {
+				data, _ := ctxManager.FetchContextData()
+				err := pwm.ExecuteWithContext(data, argsWithoutCommands(args, plugin.CommandParts()))
+				if err != nil {
+					return &runError{err: err}
+				}
+			}
+			return nil
+		}
 		err := plugin.Execute(argsWithoutCommands(args, plugin.CommandParts()))
 		if err != nil {
 			return &runError{err: err}
@@ -146,7 +164,7 @@ func filterHelpOptions(args []string) []string {
 }
 
 // Check if the plugin collides with any command specified in the root command
-func validatePlugin(root *cobra.Command, plugin plugin.Plugin) error {
+func validatePlugin(root *cobra.Command, plugin pluginpkg.Plugin) error {
 	// Check if a given plugin can be identified as a command
 	cmd, args, err := root.Find(plugin.CommandParts())
 

cmd/kn/main_test.go

@@ -21,25 +21,23 @@ import (
 	"strings"
 	"testing"
 
-	"knative.dev/client/pkg/kn/plugin"
-
 	"github.com/spf13/cobra"
 	"gotest.tools/v3/assert"
-
-	"knative.dev/client/lib/test"
-	"knative.dev/client/pkg/kn/config"
-	"knative.dev/client/pkg/kn/root"
+	"knative.dev/client/pkg/config"
+	pluginpkg "knative.dev/client/pkg/plugin"
+	"knative.dev/client/pkg/root"
 	"knative.dev/client/pkg/util"
+	"knative.dev/client/pkg/util/test"
 )
 
 func TestValidatePlugin(t *testing.T) {
 
 	// Build up simple command hierarchy
-	root := cobra.Command{}
+	rootCmd := cobra.Command{}
 	one := &cobra.Command{Use: "one"}
 	one.AddCommand(&cobra.Command{Use: "eins"}, &cobra.Command{Use: "zwei"})
 	two := &cobra.Command{Use: "two"}
-	root.AddCommand(one, two)
+	rootCmd.AddCommand(one, two)
 
 	data := []struct {
 		givenPluginCommandParts []string
@@ -84,7 +82,7 @@ func TestValidatePlugin(t *testing.T) {
 
 	for i, d := range data {
 		step := fmt.Sprintf("Check %d", i)
-		err := validatePlugin(&root, commandPartsOnlyPlugin(d.givenPluginCommandParts))
+		err := validatePlugin(&rootCmd, commandPartsOnlyPlugin(d.givenPluginCommandParts))
 		if len(d.expectedErrors) == 0 {
 			assert.NilError(t, err, step)
 		} else {
@@ -361,7 +359,7 @@ func TestRun(t *testing.T) {
 		args           []string
 		expectedOut    []string
 		expectedErrOut []string
-		plugin         plugin.Plugin
+		plugin         pluginpkg.Plugin
 	}{
 		{
 			[]string{"kn", "version"},
@@ -425,8 +423,8 @@ func TestRun(t *testing.T) {
 	for _, tc := range testCases {
 		os.Args = tc.args
 		if tc.plugin != nil {
-			plugin.InternalPlugins = plugin.PluginList{}
-			plugin.InternalPlugins = append(plugin.InternalPlugins, tc.plugin)
+			pluginpkg.InternalPlugins = pluginpkg.PluginList{}
+			pluginpkg.InternalPlugins = append(pluginpkg.InternalPlugins, tc.plugin)
 		}
 		capture := test.CaptureOutput(t)
 		err := run(tc.args[1:])

docs/README.md

@@ -1,141 +1,7 @@
 # kn
 
-`kn` is the Knative command line interface (CLI).
-
-## Getting Started
-
-### Installing `kn`
-
-You can grab the latest nightly binary executable for:
-
-- [macOS](https://storage.googleapis.com/knative-nightly/client/latest/kn-darwin-amd64)
-- [Linux](https://storage.googleapis.com/knative-nightly/client/latest/kn-linux-amd64)
-- [Windows](https://storage.googleapis.com/knative-nightly/client/latest/kn-windows-amd64.exe)
-
-Add the binary to the system PATH and ensure that it is executable.
-
-Alternatively, check out the client repository, and type:
-
-```bash
-go install ./cmd/kn
-```
-
-To use the kn container image:
-
-- Nightly: `gcr.io/knative-nightly/knative.dev/client/cmd/kn`
-- Latest release: `gcr.io/knative-releases/knative.dev/client/cmd/kn`
-
-To install `kn` using [Homebrew](https://brew.sh):
-
-```bash
-brew tap knative/client
-brew install kn
-```
-
-### Connecting to your cluster
-
-You'll need a `kubectl`-style config file to connect to your cluster.
-
-- Starting [minikube](https://github.com/kubernetes/minikube) writes this file
-  (or gives you an appropriate context in an existing config file)
-- Instructions for Google
-  [GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl)
-- Instructions for Amazon
-  [EKS](https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html)
-- Instructions for IBM
-  [IKS](https://cloud.ibm.com/docs/containers?topic=containers-getting-started)
-- Instructions for Red Hat
-  [OpenShift](https://docs.openshift.com/container-platform/4.1/cli_reference/administrator-cli-commands.html#create-kubeconfig)
-- Or contact your cluster administrator
-
-`kn` will pick up your `kubectl` config file in the default location of
-`$HOME/.kube/config`. You can specify an alternate kubeconfig connection file
-with `--kubeconfig`, or the env var `$KUBECONFIG`, for any command.
-
-## Configuration
-
-There are a set of configuration parameters you can set up to customize
-`kn`. For example, you can specify where your `kn` plugins are located and how
-they are found or add prefixes for Knative eventing sink mappings.
-
-### Location
-
-You can customize your `kn` CLI setup by creating a `config.yaml` configuration file. You can either provide the configuration via a `--config` flag or is picked up from a default location. The default configuration location conforms to the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) and is different for Unix systems and Windows systems. If `XDG_CONFIG_HOME` env var is set, the default config location `kn` looks for is `$XDG_CONFIG_HOME/kn`, otherwise the file is looked up under the home directory of the user at `$HOME/.config/kn/config.yaml`. For Windows systems, the default `kn` configuration location is `%APPDATA%\kn`.
-
-`kn` does not create a configuration file on its own, nor does it write into an existing configuration file. When `kn` does not find a configuration file it uses the default values described below.
-
-### Options
-
-Options in `config.yaml` are grouped into categories:
-
-* **Global** - Global configuration values that affect all `kn`
-* **Plugins** - Plugin related configuration values like where to find plugins (sedction `plugins:`)
-* **Eventing** - Configuration that impacts eventing related operations (section: `eventing:`)
-
-The following example contains a fully commented `config.yaml` with all available options:
-
-```yaml
-# Plugins related configuration
-plugins:
-  # Whether to lookup configuration in the execution path (default: true). This option is deprecated and will be removed in a future version where path lookup will be enabled unconditionally
-  path-lookup: true
-  # Directory from where plugins with the prefix "kn-" are looked up. (default: "$base_dir/plugins"
-  # where "$base_dir" is the directory where this configuration file is stored)
-  directory: ~/.config/kn/plugins
-# Eventing related configuration
-eventing:
-  # List of sink mappings that allow custom prefixes wherever a sink
-  # specification is used (like for the --sink option of a broker)
-  sink-mappings:
-    # Prefix as used in the command (e.g. "--sink svc:myservice")
-  - prefix: svc
-    # Api group of the mapped resource
-    group: core
-    # Api version of the mapped resource
-    version: v1
-    # Resource name (lowercased plural form of the 'kind')
-    resource: services
-  # Channel mappings that you can use in --channel options
-  channel-type-mappings:
-    # Alias that can be used as a type for a channel option (e.g. "kn create channel mychannel --type Kafka")
-  - alias: Kafka
-    # Api group of the mapped resource
-    group: messaging.knative.dev
-    # Api version of the mapped resource
-    version: v1alpha1
-    # Kind of the resource
-    kind: KafkaChannel
-```
-
-#### Plugin configuration
-
-You can specify plugin related configuration in the top-level `plugins:` sections.
-You can specify the following options:
-
-* `directory`, which is the same as the persistent flag `--plugins-dir` and specifies the kn plugins directory. It defaults to: `~/.config/kn/plugins`.
-   By using the persistent flag (when you issue a command) or by specifying the
-   value in the `kn` config, a user can select which directory to find `kn`
-   plugins. It can be any directory that is visible to the user. The plugins need have a `kn-` prefix in their name (eg. `kn-quickstart`) to be detected by `kn`
-
-* `path-lookup`, which is the same as the persistent flag
-   `--lookup-plugins-in-path` and specifies if `kn` should look for plugins anywhere in the specified `PATH` environment variable. This option is a boolean type, and the default value is `true`. This option is DEPRECATED and will be removed in a future version, when path lookup will be always enabled.
-
-#### Eventing configuration
-
-The `eventing:` top-level configuration section holds configuration options that influence the behaviour of eventing related commands.
-
-* `sink-mappings` defines prefixes to refer to Kubernetes _Addressable_ resources as
-   used in `--sink` kind of options. `sink-mappings refers to an array of individual mapping definitions that you can configure with these fields:
-   - `prefix`: Prefix you want to describe your sink as. `ksvc` (`serving.knative.dev/v1`), `broker` (`eventing.knative.dev/v1`) and `channel` (`messaging.knative.dev/v1`) are predefined prefixes. Values in the configuration file can override these predefined prefixes.
-   - `group`: The APIGroup of Kubernetes resource.
-   - `version`: The version of Kubernetes resources.
-   - `resource`: The plural name of Kubernetes resources (for example: `services`).
-
-* `channel-type-mappings` can be used to define aliases for custom channel types that can be used wherever a channel type is required (as in `kn channel create --type`). This configuration section defines an array of entries with the following fields:
-   - `alias`: The name that can be used as the type
-   - `group`: The APIGroup of the channel CRD.
-   - `version`: The version of the channel CRD.
-   - `kind`: Kind of the channel CRD (e.g. `KafkaChannel`)
+`kn` is the Knative command line interface (CLI). Check out the
+[official documentation](https://knative.dev/docs/client/).
   
 ## Commands
 

docs/cmd/kn.md

@@ -11,12 +11,15 @@ Find more information about Knative at: https://knative.dev
 ### Options
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-  -h, --help                help for kn
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+  -h, --help                   help for kn
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO
@@ -31,6 +34,7 @@ Find more information about Knative at: https://knative.dev
 * [kn plugin](kn_plugin.md)	 - Manage kn plugins
 * [kn revision](kn_revision.md)	 - Manage service revisions
 * [kn route](kn_route.md)	 - List and describe service routes
+* [kn secret](kn_secret.md)	 - Manage secrets
 * [kn service](kn_service.md)	 - Manage Knative services
 * [kn source](kn_source.md)	 - Manage event sources
 * [kn subscription](kn_subscription.md)	 - Manage event subscriptions

docs/cmd/kn_broker.md

@@ -15,11 +15,14 @@ kn broker
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO
@@ -29,4 +32,5 @@ kn broker
 * [kn broker delete](kn_broker_delete.md)	 - Delete a broker
 * [kn broker describe](kn_broker_describe.md)	 - Describe broker
 * [kn broker list](kn_broker_list.md)	 - List brokers
+* [kn broker update](kn_broker_update.md)	 - Update a broker
 

docs/cmd/kn_broker_create.md

@@ -16,24 +16,50 @@ kn broker create NAME
   # Create a broker 'mybroker' in the 'myproject' namespace and with a broker class of 'Kafka'
   kn broker create mybroker --namespace myproject --class Kafka
 
+  # Create a broker 'mybroker' in the myproject namespace with config referencing a configmap in current namespace
+  kn broker create mybroker --namespace myproject --class Kafka --broker-config cm:spec-cm
+  OR
+  kn broker create mybroker --namespace myproject --class Kafka --broker-config spec-cm
+
+  # Create a broker 'mybroker' in the myproject namespace with config referencing secret named spec-sc in test namespace
+  kn broker create mybroker --namespace myproject --class Kafka --broker-config sc:spec-sc:test
+
+  # Create a broker 'mybroker' in the myproject namespace with config referencing RabbitmqCluster mycluster in test namespace
+  kn broker create mybroker --namespace myproject --class Kafka --broker-config rabbitmq.com/v1beta1:RabbitmqCluster:mycluster:test
+
 ```
 
 ### Options
 
 ```
-      --class string       Broker class like 'MTChannelBasedBroker' or 'Kafka' (if available)
-  -h, --help               help for create
-  -n, --namespace string   Specify the namespace to operate in.
+      --backoff-delay string     The delay before retrying.
+      --backoff-policy string    The retry backoff policy (linear, exponential).
+      --broker-config string     Reference to the broker configuration For example, a pointer to a ConfigMap (cm:, configmap:), Secret(sc:, secret:), RabbitmqCluster(rmq:, rabbitmq: rabbitmqcluster:) etc. It should be used in conjunction with --class flag. The format for specifying the object is a colon separated string consisting of at most 4 slices:
+                                 Length 1: <object-name> (the object will be assumed to be ConfigMap with the same name)
+                                 Length 2: <kind>:<object-name> (the APIVersion will be determined for ConfigMap, Secret, and RabbitmqCluster types)
+                                 Length 3: <kind>:<object-name>:<namespace> (the APIVersion will be determined only for ConfigMap, Secret, and RabbitmqCluster types. Otherwise it will be interpreted as:
+                                 <apiVersion>:<kind>:<object-name>)
+                                 Length 4: <apiVersion>:<kind>:<object-name>:<namespace>
+      --class string             Broker class like 'MTChannelBasedBroker' or 'Kafka' (if available).
+      --dl-sink string           The sink receiving event that could not be sent to a destination.
+  -h, --help                     help for create
+  -n, --namespace string         Specify the namespace to operate in.
+      --retry int32              The minimum number of retries the sender should attempt when sending an event before moving it to the dead letter sink.
+      --retry-after-max string   An optional upper bound on the duration specified in a "Retry-After" header when calculating backoff times for retrying 429 and 503 response codes. Setting the value to zero ("PT0S") can be used to opt-out of respecting "Retry-After" header values altogether. This value only takes effect if "Retry" is configured, and also depends on specific implementations (Channels, Sources, etc.) choosing to provide this capability.
+      --timeout string           The timeout of each single request. The value must be greater than 0.
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_broker_delete.md

@@ -25,16 +25,20 @@ kn broker delete NAME
       --no-wait            Do not wait for 'broker delete' operation to be completed. (default true)
       --wait               Wait for 'broker delete' operation to be completed.
       --wait-timeout int   Seconds to wait before giving up on waiting for broker to be deleted. (default 600)
+      --wait-window int    Seconds to wait for broker to be deleted after a false ready condition is returned (default 2)
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_broker_describe.md

@@ -37,11 +37,14 @@ kn broker describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_broker_list.md

@@ -25,7 +25,7 @@ kn broker list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -33,11 +33,14 @@ kn broker list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_broker_update.md

@@ -0,0 +1,50 @@
+## kn broker update
+
+Update a broker
+
+```
+kn broker update NAME
+```
+
+### Examples
+
+```
+
+  # Update a broker 'mybroker' in the current namespace with delivery sink svc1
+  kn broker update mybroker --dl-sink svc1
+
+  # Update a broker 'mybroker' in the 'myproject' namespace and with retry 2 seconds
+  kn broker update mybroker --namespace myproject --retry 2
+
+```
+
+### Options
+
+```
+      --backoff-delay string     The delay before retrying.
+      --backoff-policy string    The retry backoff policy (linear, exponential).
+      --dl-sink string           The sink receiving event that could not be sent to a destination.
+  -h, --help                     help for update
+  -n, --namespace string         Specify the namespace to operate in.
+      --retry int32              The minimum number of retries the sender should attempt when sending an event before moving it to the dead letter sink.
+      --retry-after-max string   An optional upper bound on the duration specified in a "Retry-After" header when calculating backoff times for retrying 429 and 503 response codes. Setting the value to zero ("PT0S") can be used to opt-out of respecting "Retry-After" header values altogether. This value only takes effect if "Retry" is configured, and also depends on specific implementations (Channels, Sources, etc.) choosing to provide this capability.
+      --timeout string           The timeout of each single request. The value must be greater than 0.
+```
+
+### Options inherited from parent commands
+
+```
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
+```
+
+### SEE ALSO
+
+* [kn broker](kn_broker.md)	 - Manage message brokers
+

docs/cmd/kn_channel.md

@@ -15,11 +15,14 @@ kn channel COMMAND
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_channel_create.md

@@ -19,7 +19,7 @@ kn channel create NAME
   kn channel create imc1 --type messaging.knative.dev:v1:InMemoryChannel
 
   # Create a channel 'k1' of type KafkaChannel
-  kn channel create k1 --type messaging.knative.dev:v1alpha1:KafkaChannel
+  kn channel create k1 --type messaging.knative.dev:v1beta1:KafkaChannel
 ```
 
 ### Options
@@ -27,17 +27,20 @@ kn channel create NAME
 ```
   -h, --help               help for create
   -n, --namespace string   Specify the namespace to operate in.
-      --type string        Override channel type to create, in the format '--type Group:Version:Kind'. If flag is not specified, it uses default messaging layer settings for channel type, cluster wide or specific namespace. You can configure aliases for channel types in kn config and refer the aliases with this flag. You can also refer inbuilt channel type InMemoryChannel using an alias 'imc' like '--type imc'. Examples: '--type messaging.knative.dev:v1alpha1:KafkaChannel' for specifying explicit Group:Version:Kind.
+      --type string        Override channel type to create, in the format '--type Group:Version:Kind'. If flag is not specified, it uses default messaging layer settings for channel type, cluster wide or specific namespace. You can configure aliases for channel types in kn config and refer the aliases with this flag. You can also refer inbuilt channel type InMemoryChannel using an alias 'imc' like '--type imc'. Examples: '--type messaging.knative.dev:v1beta1:KafkaChannel' for specifying explicit Group:Version:Kind.
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_channel_delete.md

@@ -24,11 +24,14 @@ kn channel delete NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_channel_describe.md

@@ -32,11 +32,14 @@ kn channel describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_channel_list-types.md

@@ -24,7 +24,7 @@ kn channel list-types
   -h, --help                          help for list-types
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -32,11 +32,14 @@ kn channel list-types
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_channel_list.md

@@ -25,7 +25,7 @@ kn channel list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -33,11 +33,14 @@ kn channel list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_completion.md

@@ -10,6 +10,8 @@ to provide interactive completion
 
 Supported Shells:
  - bash
+ - fish
+ - powershell
  - zsh
 
 ```
@@ -23,6 +25,12 @@ kn completion SHELL
  # Generate completion code for bash
  source <(kn completion bash)
 
+ # Generate completion code for fish
+ kn completion fish | source
+
+ # Generate completion code for powershell
+ kn completion powershell | Out-String | Invoke-Expression
+
  # Generate completion code for zsh
  source <(kn completion zsh)
  compdef _kn kn
@@ -37,11 +45,14 @@ kn completion SHELL
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_container.md

@@ -15,11 +15,14 @@ kn container COMMAND
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_container_add.md

@@ -28,32 +28,44 @@ kn container add NAME
 ### Options
 
 ```
-      --arg stringArray              Add argument to the container command. Example: --arg myArg1 --arg --myArg2 --arg myArg3=3. You can use this flag multiple times.
-      --cmd stringArray              Specify command to be used as entrypoint instead of default one. Example: --cmd /app/start or --cmd sh --cmd /app/start.sh or --cmd /app/start --arg myArg to pass additional arguments.
-      --containers string            Specify path to file including definition for additional containers, alternatively use '-' to read from stdin. Example: --containers ./containers.yaml or --containers -.
-  -e, --env stringArray              Environment variable to set. NAME=value; you may provide this flag any number of times to set multiple environment variables. To unset, specify the environment variable name followed by a "-" (e.g., NAME-).
-      --env-file string              Path to a file containing environment variables (e.g. --env-file=/home/knative/service1/env).
-      --env-from stringArray         Add environment variables from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret:). Example: --env-from cm:myconfigmap or --env-from secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --env-from cm:myconfigmap-.
-      --env-value-from stringArray   Add environment variable from a value of key in ConfigMap (prefix cm: or config-map:) or a Secret (prefix sc: or secret:). Example: --env-value-from NAME=cm:myconfigmap:key or --env-value-from NAME=secret:mysecret:key. You can use this flag multiple times. To unset a value from a ConfigMap/Secret key reference, append "-" to the key, e.g. --env-value-from ENV-.
-  -h, --help                         help for add
-      --image string                 Image to run.
-      --limit strings                The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
-      --mount stringArray            Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
-  -p, --port string                  The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
-      --pull-secret string           Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
-      --request strings              The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
-      --service-account string       Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
-      --user int                     The user ID to run the container (e.g., 1001).
+      --arg stringArray               Add argument to the container command. Example: --arg myArg1 --arg --myArg2 --arg myArg3=3. You can use this flag multiple times.
+      --cmd stringArray               Specify command to be used as entrypoint instead of default one. Example: --cmd /app/start or --cmd sh --cmd /app/start.sh or --cmd /app/start --arg myArg to pass additional arguments.
+      --containers string             Specify path to file including definition for additional containers, alternatively use '-' to read from stdin. Example: --containers ./containers.yaml or --containers -.
+  -e, --env stringArray               Environment variable to set. NAME=value; you may provide this flag any number of times to set multiple environment variables. To unset, specify the environment variable name followed by a "-" (e.g., NAME-).
+      --env-file string               Path to a file containing environment variables (e.g. --env-file=/home/knative/service1/env).
+      --env-from stringArray          Add environment variables from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret:). Example: --env-from cm:myconfigmap or --env-from secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --env-from cm:myconfigmap-.
+      --env-value-from stringArray    Add environment variable from a value of key in ConfigMap (prefix cm: or config-map:) or a Secret (prefix sc: or secret:). Example: --env-value-from NAME=cm:myconfigmap:key or --env-value-from NAME=secret:mysecret:key. You can use this flag multiple times. To unset a value from a ConfigMap/Secret key reference, append "-" to the key, e.g. --env-value-from ENV-.
+  -h, --help                          help for add
+      --image string                  Image to run.
+      --limit strings                 The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
+      --mount stringArray             Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:), a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim) or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, --mount /mydir=emptyDir:myvol or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can mount a volume with readOnly config (true | false) also. Example: --mount /mydir=ed:ed1:readOnly=true. You can specify a volume subpath by following the volume name with slash separated path. Example: --mount /mydir=cm:myconfigmap/subpath/to/be/mounted. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
+      --node-affinity strings         Add node affinity to be set - only works if the feature gate is enabled in Knative Serving feature flags configuration. When key, operator, values (whitespace separated) and weight are defined for a type, they will be appended in nodeSelectorTerms in case of Required clause, implying the terms will be ORed, and for Preferred clause, all of them will be added in preferredDuringSchedulingIgnoredDuringExecution. Example: --node-affinity Type="Required",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1 antarctica-west1" or --node-affinity Type="Preferred",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1",Weight="1"
+      --node-selector stringArray     Add node selector to be set, you may provide this flag any number of times to set multiple node selectors, works if feature flag is enabled in Knative Serving feature flags configuration. Example: --node-selector Disktype="ssd". To unset, specify the key name followed by a "-", example: --node-selector Disktype- .
+  -p, --port string                   The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
+      --probe-liveness string         Add liveness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-liveness-opts string    Add common options to liveness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --probe-readiness string        Add readiness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-readiness-opts string   Add common options to readiness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --pull-policy string            Image pull policy. Valid values (case insensitive): Always | Never | IfNotPresent
+      --pull-secret string            Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
+      --request strings               The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
+      --security-context string       Predefined security context for the service. Accepted values: 'none' for no security context and 'strict' for dropping all capabilities, running as non-root, and no privilege escalation. (default "none")
+      --service-account string        Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
+      --toleration strings            Add toleration to be set, works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --tolerations Key="key1",Operator="Equal",Value="value1",Effect="NoSchedule"
+      --user int                      The user ID to run the container (e.g., 1001).
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_domain.md

@@ -15,11 +15,14 @@ kn domain COMMAND
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_domain_create.md

@@ -26,11 +26,14 @@ kn domain create NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_domain_delete.md

@@ -24,11 +24,14 @@ kn domain delete NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_domain_describe.md

@@ -29,11 +29,14 @@ kn domain describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_domain_list.md

@@ -25,7 +25,7 @@ kn domain list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -33,11 +33,14 @@ kn domain list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_domain_update.md

@@ -25,11 +25,14 @@ kn domain update NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_eventtype.md

@@ -15,11 +15,14 @@ kn eventtype
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_eventtype_create.md

@@ -21,9 +21,10 @@ kn eventtype create
 ### Options
 
 ```
-  -b, --broker string      Cloud Event broker
+  -b, --broker string      Cloud Event Broker
   -h, --help               help for create
   -n, --namespace string   Specify the namespace to operate in.
+  -r, --reference string   Addressable Reference producing events. You can specify a broker, channel, or fully qualified GroupVersionResource (GVR). Examples: '--reference broker:nest' for a broker 'nest', '--reference channel:pipe' for a channel 'pipe', '--reference special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'.
       --source string      Cloud Event source
   -t, --type string        Cloud Event type
 ```
@@ -31,11 +32,14 @@ kn eventtype create
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_eventtype_delete.md

@@ -28,11 +28,14 @@ kn eventtype delete
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_eventtype_describe.md

@@ -34,11 +34,14 @@ kn eventtype describe
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_eventtype_list.md

@@ -25,7 +25,7 @@ kn eventtype list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -33,11 +33,14 @@ kn eventtype list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_options.md

@@ -26,11 +26,14 @@ kn options
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_plugin.md

@@ -22,11 +22,14 @@ kn plugin
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_plugin_list.md

@@ -26,11 +26,14 @@ kn plugin list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_revision.md

@@ -15,11 +15,14 @@ kn revision
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_revision_delete.md

@@ -30,16 +30,20 @@ kn revision delete NAME [NAME ...]
       --prune-all          Remove all unreferenced revisions in a namespace.
       --wait               Wait for 'revision delete' operation to be completed.
       --wait-timeout int   Seconds to wait before giving up on waiting for revision to be deleted. (default 600)
+      --wait-window int    Seconds to wait for revision to be deleted after a false ready condition is returned (default 2)
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_revision_describe.md

@@ -12,7 +12,7 @@ kn revision describe NAME
       --allow-missing-template-keys   If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
   -h, --help                          help for describe
   -n, --namespace string              Specify the namespace to operate in.
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
   -v, --verbose                       More output.
@@ -21,11 +21,14 @@ kn revision describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_revision_list.md

@@ -35,7 +35,7 @@ kn revision list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
   -s, --service string                Service name
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
@@ -44,11 +44,14 @@ kn revision list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_route.md

@@ -15,11 +15,14 @@ kn route
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_route_describe.md

@@ -12,7 +12,7 @@ kn route describe NAME
       --allow-missing-template-keys   If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
   -h, --help                          help for describe
   -n, --namespace string              Specify the namespace to operate in.
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
   -v, --verbose                       More output.
@@ -21,11 +21,14 @@ kn route describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_route_list.md

@@ -28,7 +28,7 @@ kn route list NAME
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -36,11 +36,14 @@ kn route list NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_secret.md

@@ -0,0 +1,34 @@
+## kn secret
+
+Manage secrets
+
+```
+kn secret COMMAND
+```
+
+### Options
+
+```
+  -h, --help   help for secret
+```
+
+### Options inherited from parent commands
+
+```
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
+```
+
+### SEE ALSO
+
+* [kn](kn.md)	 - kn manages Knative Serving and Eventing resources
+* [kn secret create](kn_secret_create.md)	 - Create secret
+* [kn secret delete](kn_secret_delete.md)	 - Delete secret
+* [kn secret list](kn_secret_list.md)	 - List secrets
+

docs/cmd/kn_secret_create.md

@@ -0,0 +1,36 @@
+## kn secret create
+
+Create secret
+
+```
+kn secret create NAME
+```
+
+### Options
+
+```
+  -l, --from-literal strings   Specify comma separated list of key=value pairs.
+  -h, --help                   help for create
+  -n, --namespace string       Specify the namespace to operate in.
+      --tls-cert string        Path to TLS certificate file.
+      --tls-key string         Path to TLS key file.
+      --type string            Specify Secret type.
+```
+
+### Options inherited from parent commands
+
+```
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
+```
+
+### SEE ALSO
+
+* [kn secret](kn_secret.md)	 - Manage secrets
+

docs/cmd/kn_secret_delete.md

@@ -0,0 +1,32 @@
+## kn secret delete
+
+Delete secret
+
+```
+kn secret delete NAME
+```
+
+### Options
+
+```
+  -h, --help               help for delete
+  -n, --namespace string   Specify the namespace to operate in.
+```
+
+### Options inherited from parent commands
+
+```
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
+```
+
+### SEE ALSO
+
+* [kn secret](kn_secret.md)	 - Manage secrets
+

docs/cmd/kn_secret_list.md

@@ -0,0 +1,37 @@
+## kn secret list
+
+List secrets
+
+```
+kn secret list
+```
+
+### Options
+
+```
+      --allow-missing-template-keys   If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
+  -h, --help                          help for list
+  -n, --namespace string              Specify the namespace to operate in.
+      --no-headers                    When using the default output format, don't print headers (default: print headers).
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
+      --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
+      --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
+```
+
+### Options inherited from parent commands
+
+```
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
+```
+
+### SEE ALSO
+
+* [kn secret](kn_secret.md)	 - Manage secrets
+

docs/cmd/kn_service.md

@@ -15,11 +15,14 @@ kn service
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO
@@ -33,4 +36,5 @@ kn service
 * [kn service import](kn_service_import.md)	 - Import a service and its revisions (experimental)
 * [kn service list](kn_service_list.md)	 - List services
 * [kn service update](kn_service_update.md)	 - Update a service
+* [kn service wait](kn_service_wait.md)	 - Wait for a service to be ready
 

docs/cmd/kn_service_apply.md

@@ -50,37 +50,54 @@ kn service apply s0 --filename my-svc.yml
       --label-service stringArray         Service label to set. name=value; you may provide this flag any number of times to set multiple labels. To unset, specify the label name followed by a "-" (e.g., name-). This flag takes precedence over the "label" flag.
       --limit strings                     The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
       --lock-to-digest                    Keep the running image for the service constant when not explicitly specifying the image. (--no-lock-to-digest pulls the image tag afresh with each new revision) (default true)
-      --mount stringArray                 Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
+      --mount stringArray                 Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:), a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim) or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, --mount /mydir=emptyDir:myvol or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can mount a volume with readOnly config (true | false) also. Example: --mount /mydir=ed:ed1:readOnly=true. You can specify a volume subpath by following the volume name with slash separated path. Example: --mount /mydir=cm:myconfigmap/subpath/to/be/mounted. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
   -n, --namespace string                  Specify the namespace to operate in.
       --no-cluster-local                  Do not specify that the service be private. (--no-cluster-local will make the service publicly available) (default true)
       --no-lock-to-digest                 Do not keep the running image for the service constant when not explicitly specifying the image. (--no-lock-to-digest pulls the image tag afresh with each new revision)
       --no-wait                           Do not wait for 'service apply' operation to be completed.
+      --node-affinity strings             Add node affinity to be set - only works if the feature gate is enabled in Knative Serving feature flags configuration. When key, operator, values (whitespace separated) and weight are defined for a type, they will be appended in nodeSelectorTerms in case of Required clause, implying the terms will be ORed, and for Preferred clause, all of them will be added in preferredDuringSchedulingIgnoredDuringExecution. Example: --node-affinity Type="Required",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1 antarctica-west1" or --node-affinity Type="Preferred",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1",Weight="1"
+      --node-selector stringArray         Add node selector to be set, you may provide this flag any number of times to set multiple node selectors, works if feature flag is enabled in Knative Serving feature flags configuration. Example: --node-selector Disktype="ssd". To unset, specify the key name followed by a "-", example: --node-selector Disktype- .
   -p, --port string                       The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
+      --probe-liveness string             Add liveness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-liveness-opts string        Add common options to liveness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --probe-readiness string            Add readiness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-readiness-opts string       Add common options to readiness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --profile string                    The profile name must be defined in config.yaml or part of the built-in profile, e.g. Istio. Related annotations and labels will be added to the service.To unset, specify the profile name followed by a "-" (e.g., name-).
+      --pull-policy string                Image pull policy. Valid values (case insensitive): Always | Never | IfNotPresent
       --pull-secret string                Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
       --request strings                   The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
       --revision-name string              The revision name to set. Must start with the service name and a dash as a prefix. Empty revision name will result in the server generating a name for the revision. Accepts golang templates, allowing {{.Service}} for the service name, {{.Generation}} for the generation, and {{.Random [n]}} for n random consonants (e.g. {{.Service}}-{{.Random 5}}-{{.Generation}})
       --scale string                      Set the Minimum and Maximum number of replicas. You can use this flag to set both to a single value, or set a range with min/max values, or set either min or max values without specifying the other. Example: --scale 5 (scale-min = 5, scale-max = 5) or --scale 1..5 (scale-min = 1, scale-max = 5) or --scale 1.. (scale-min = 1, scale-max = unchanged) or --scale ..5 (scale-min = unchanged, scale-max = 5)
+      --scale-activation int              Minimum non-zero value that a service should scale to.
       --scale-init int                    Initial number of replicas with which a service starts. Can be 0 or a positive integer.
       --scale-max int                     Maximum number of replicas.
+      --scale-metric string               Set the name of the metric the PodAutoscaler should scale on. Example: --scale-metric rps (to scale on rps) or --scale-metric concurrency (to scale on concurrency). The default metric is concurrency.
       --scale-min int                     Minimum number of replicas.
-      --scale-target int                  Recommendation for when to scale up based on the concurrent number of incoming request. Defaults to --concurrency-limit when given.
+      --scale-target int                  Recommendation for what metric value the PodAutoscaler should attempt to maintain. Use with --scale-metric flag to configure the metric name for which the target value should be maintained. Default metric name is concurrency. The flag defaults to --concurrency-limit when given.
       --scale-utilization int             Percentage of concurrent requests utilization before scaling up. (default 70)
       --scale-window string               Duration to look back for making auto-scaling decisions. The service is scaled to zero if no request was received in during that time. (eg: 10s)
+      --security-context string           Predefined security context for the service. Accepted values: 'none' for no security context and 'strict' for dropping all capabilities, running as non-root, and no privilege escalation. (default "none")
       --service-account string            Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
+      --timeout int                       Duration in seconds that the request routing layer will wait for a request delivered to a container to begin replying (default 300)
+      --toleration strings                Add toleration to be set, works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --tolerations Key="key1",Operator="Equal",Value="value1",Effect="NoSchedule"
       --user int                          The user ID to run the container (e.g., 1001).
-      --volume stringArray                Add a volume from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret: or sc:). Example: --volume myvolume=cm:myconfigmap or --volume myvolume=secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
+      --volume stringArray                Add a volume from a ConfigMap (prefix cm: or config-map:) a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:) or a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim). PersistentVolumeClaim only works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --volume myvolume=cm:myconfigmap, --volume myvolume=secret:mysecret or --volume emptyDir:myvol:size=1Gi,type=Memory. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
       --wait                              Wait for 'service apply' operation to be completed. (default true)
       --wait-timeout int                  Seconds to wait before giving up on waiting for service to be ready. (default 600)
+      --wait-window int                   Seconds to wait for service to be ready after a false ready condition is returned (default 2)
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_create.md

@@ -49,6 +49,18 @@ kn service create NAME --image IMAGE
   kn service create gitopstest -n test-ns --image knativesamples/helloworld --target=/user/knfiles
   kn service create gitopstest --image knativesamples/helloworld --target=/user/knfiles/test.yaml
   kn service create gitopstest --image knativesamples/helloworld --target=/user/knfiles/test.json
+
+  # Create a service with profile
+  kn service create profiletest --image knativesamples/helloworld --profile istio
+
+  # Create a service with node selector
+  kn service create nodeselectortest --image knativesamples/helloworld --node-selector Disktype="ssd"
+
+  # Create a service with toleration
+  kn service create tolerationtest --image knativesamples/helloworld --toleration Key="node-role.kubernetes.io/master",Effect="NoSchedule",Operator="Equal",Value=""
+
+  # Create a service with node affinity
+  kn service create nodeaffinitytest --image knativesamples/helloworld --node-affinity Type="Required",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1 antarctica-east2"
 ```
 
 ### Options
@@ -75,39 +87,56 @@ kn service create NAME --image IMAGE
       --label-service stringArray         Service label to set. name=value; you may provide this flag any number of times to set multiple labels. To unset, specify the label name followed by a "-" (e.g., name-). This flag takes precedence over the "label" flag.
       --limit strings                     The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
       --lock-to-digest                    Keep the running image for the service constant when not explicitly specifying the image. (--no-lock-to-digest pulls the image tag afresh with each new revision) (default true)
-      --mount stringArray                 Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
+      --mount stringArray                 Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:), a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim) or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, --mount /mydir=emptyDir:myvol or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can mount a volume with readOnly config (true | false) also. Example: --mount /mydir=ed:ed1:readOnly=true. You can specify a volume subpath by following the volume name with slash separated path. Example: --mount /mydir=cm:myconfigmap/subpath/to/be/mounted. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
   -n, --namespace string                  Specify the namespace to operate in.
       --no-cluster-local                  Do not specify that the service be private. (--no-cluster-local will make the service publicly available) (default true)
       --no-lock-to-digest                 Do not keep the running image for the service constant when not explicitly specifying the image. (--no-lock-to-digest pulls the image tag afresh with each new revision)
       --no-wait                           Do not wait for 'service create' operation to be completed.
+      --node-affinity strings             Add node affinity to be set - only works if the feature gate is enabled in Knative Serving feature flags configuration. When key, operator, values (whitespace separated) and weight are defined for a type, they will be appended in nodeSelectorTerms in case of Required clause, implying the terms will be ORed, and for Preferred clause, all of them will be added in preferredDuringSchedulingIgnoredDuringExecution. Example: --node-affinity Type="Required",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1 antarctica-west1" or --node-affinity Type="Preferred",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1",Weight="1"
+      --node-selector stringArray         Add node selector to be set, you may provide this flag any number of times to set multiple node selectors, works if feature flag is enabled in Knative Serving feature flags configuration. Example: --node-selector Disktype="ssd". To unset, specify the key name followed by a "-", example: --node-selector Disktype- .
   -p, --port string                       The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
+      --probe-liveness string             Add liveness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-liveness-opts string        Add common options to liveness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --probe-readiness string            Add readiness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-readiness-opts string       Add common options to readiness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --profile string                    The profile name must be defined in config.yaml or part of the built-in profile, e.g. Istio. Related annotations and labels will be added to the service.To unset, specify the profile name followed by a "-" (e.g., name-).
+      --pull-policy string                Image pull policy. Valid values (case insensitive): Always | Never | IfNotPresent
       --pull-secret string                Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
       --request strings                   The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
       --revision-name string              The revision name to set. Must start with the service name and a dash as a prefix. Empty revision name will result in the server generating a name for the revision. Accepts golang templates, allowing {{.Service}} for the service name, {{.Generation}} for the generation, and {{.Random [n]}} for n random consonants (e.g. {{.Service}}-{{.Random 5}}-{{.Generation}})
       --scale string                      Set the Minimum and Maximum number of replicas. You can use this flag to set both to a single value, or set a range with min/max values, or set either min or max values without specifying the other. Example: --scale 5 (scale-min = 5, scale-max = 5) or --scale 1..5 (scale-min = 1, scale-max = 5) or --scale 1.. (scale-min = 1, scale-max = unchanged) or --scale ..5 (scale-min = unchanged, scale-max = 5)
+      --scale-activation int              Minimum non-zero value that a service should scale to.
       --scale-init int                    Initial number of replicas with which a service starts. Can be 0 or a positive integer.
       --scale-max int                     Maximum number of replicas.
+      --scale-metric string               Set the name of the metric the PodAutoscaler should scale on. Example: --scale-metric rps (to scale on rps) or --scale-metric concurrency (to scale on concurrency). The default metric is concurrency.
       --scale-min int                     Minimum number of replicas.
-      --scale-target int                  Recommendation for when to scale up based on the concurrent number of incoming request. Defaults to --concurrency-limit when given.
+      --scale-target int                  Recommendation for what metric value the PodAutoscaler should attempt to maintain. Use with --scale-metric flag to configure the metric name for which the target value should be maintained. Default metric name is concurrency. The flag defaults to --concurrency-limit when given.
       --scale-utilization int             Percentage of concurrent requests utilization before scaling up. (default 70)
       --scale-window string               Duration to look back for making auto-scaling decisions. The service is scaled to zero if no request was received in during that time. (eg: 10s)
+      --security-context string           Predefined security context for the service. Accepted values: 'none' for no security context and 'strict' for dropping all capabilities, running as non-root, and no privilege escalation. (default "none")
       --service-account string            Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
       --tag strings                       Set tag (format: --tag revisionRef=tagName) where revisionRef can be a revision or '@latest' string representing latest ready revision. This flag can be specified multiple times.
       --target string                     Work on local directory instead of a remote cluster (experimental)
+      --timeout int                       Duration in seconds that the request routing layer will wait for a request delivered to a container to begin replying (default 300)
+      --toleration strings                Add toleration to be set, works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --tolerations Key="key1",Operator="Equal",Value="value1",Effect="NoSchedule"
       --user int                          The user ID to run the container (e.g., 1001).
-      --volume stringArray                Add a volume from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret: or sc:). Example: --volume myvolume=cm:myconfigmap or --volume myvolume=secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
+      --volume stringArray                Add a volume from a ConfigMap (prefix cm: or config-map:) a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:) or a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim). PersistentVolumeClaim only works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --volume myvolume=cm:myconfigmap, --volume myvolume=secret:mysecret or --volume emptyDir:myvol:size=1Gi,type=Memory. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
       --wait                              Wait for 'service create' operation to be completed. (default true)
       --wait-timeout int                  Seconds to wait before giving up on waiting for service to be ready. (default 600)
+      --wait-window int                   Seconds to wait for service to be ready after a false ready condition is returned (default 2)
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_delete.md

@@ -35,16 +35,20 @@ kn service delete NAME [NAME ...]
       --target string      Work on local directory instead of a remote cluster (experimental)
       --wait               Wait for 'service delete' operation to be completed.
       --wait-timeout int   Seconds to wait before giving up on waiting for service to be deleted. (default 600)
+      --wait-window int    Seconds to wait for service to be deleted after a false ready condition is returned (default 2)
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_describe.md

@@ -41,11 +41,14 @@ kn service describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_export.md

@@ -30,7 +30,7 @@ kn service export NAME
   -h, --help                          help for export
       --mode string                   Format for exporting all routed revisions. One of replay|export (Beta)
   -n, --namespace string              Specify the namespace to operate in.
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
       --with-revisions                Export all routed revisions (Beta)
@@ -39,11 +39,14 @@ kn service export NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_import.md

@@ -25,16 +25,20 @@ kn service import FILENAME
       --no-wait            Do not wait for 'service import' operation to be completed.
       --wait               Wait for 'service import' operation to be completed. (default true)
       --wait-timeout int   Seconds to wait before giving up on waiting for service to be ready. (default 600)
+      --wait-window int    Seconds to wait for service to be ready after a false ready condition is returned (default 2)
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_list.md

@@ -34,7 +34,7 @@ kn service list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --target string                 Work on local directory instead of a remote cluster (experimental)
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
@@ -43,11 +43,14 @@ kn service list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_update.md

@@ -62,41 +62,58 @@ kn service update NAME
       --label-service stringArray         Service label to set. name=value; you may provide this flag any number of times to set multiple labels. To unset, specify the label name followed by a "-" (e.g., name-). This flag takes precedence over the "label" flag.
       --limit strings                     The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
       --lock-to-digest                    Keep the running image for the service constant when not explicitly specifying the image. (--no-lock-to-digest pulls the image tag afresh with each new revision) (default true)
-      --mount stringArray                 Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
+      --mount stringArray                 Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:), a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim) or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, --mount /mydir=emptyDir:myvol or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can mount a volume with readOnly config (true | false) also. Example: --mount /mydir=ed:ed1:readOnly=true. You can specify a volume subpath by following the volume name with slash separated path. Example: --mount /mydir=cm:myconfigmap/subpath/to/be/mounted. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
   -n, --namespace string                  Specify the namespace to operate in.
       --no-cluster-local                  Do not specify that the service be private. (--no-cluster-local will make the service publicly available) (default true)
       --no-lock-to-digest                 Do not keep the running image for the service constant when not explicitly specifying the image. (--no-lock-to-digest pulls the image tag afresh with each new revision)
       --no-wait                           Do not wait for 'service update' operation to be completed.
+      --node-affinity strings             Add node affinity to be set - only works if the feature gate is enabled in Knative Serving feature flags configuration. When key, operator, values (whitespace separated) and weight are defined for a type, they will be appended in nodeSelectorTerms in case of Required clause, implying the terms will be ORed, and for Preferred clause, all of them will be added in preferredDuringSchedulingIgnoredDuringExecution. Example: --node-affinity Type="Required",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1 antarctica-west1" or --node-affinity Type="Preferred",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1",Weight="1"
+      --node-selector stringArray         Add node selector to be set, you may provide this flag any number of times to set multiple node selectors, works if feature flag is enabled in Knative Serving feature flags configuration. Example: --node-selector Disktype="ssd". To unset, specify the key name followed by a "-", example: --node-selector Disktype- .
   -p, --port string                       The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
+      --probe-liveness string             Add liveness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-liveness-opts string        Add common options to liveness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --probe-readiness string            Add readiness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-readiness-opts string       Add common options to readiness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --profile string                    The profile name must be defined in config.yaml or part of the built-in profile, e.g. Istio. Related annotations and labels will be added to the service.To unset, specify the profile name followed by a "-" (e.g., name-).
+      --pull-policy string                Image pull policy. Valid values (case insensitive): Always | Never | IfNotPresent
       --pull-secret string                Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
       --request strings                   The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
       --revision-name string              The revision name to set. Must start with the service name and a dash as a prefix. Empty revision name will result in the server generating a name for the revision. Accepts golang templates, allowing {{.Service}} for the service name, {{.Generation}} for the generation, and {{.Random [n]}} for n random consonants (e.g. {{.Service}}-{{.Random 5}}-{{.Generation}})
       --scale string                      Set the Minimum and Maximum number of replicas. You can use this flag to set both to a single value, or set a range with min/max values, or set either min or max values without specifying the other. Example: --scale 5 (scale-min = 5, scale-max = 5) or --scale 1..5 (scale-min = 1, scale-max = 5) or --scale 1.. (scale-min = 1, scale-max = unchanged) or --scale ..5 (scale-min = unchanged, scale-max = 5)
+      --scale-activation int              Minimum non-zero value that a service should scale to.
       --scale-init int                    Initial number of replicas with which a service starts. Can be 0 or a positive integer.
       --scale-max int                     Maximum number of replicas.
+      --scale-metric string               Set the name of the metric the PodAutoscaler should scale on. Example: --scale-metric rps (to scale on rps) or --scale-metric concurrency (to scale on concurrency). The default metric is concurrency.
       --scale-min int                     Minimum number of replicas.
-      --scale-target int                  Recommendation for when to scale up based on the concurrent number of incoming request. Defaults to --concurrency-limit when given.
+      --scale-target int                  Recommendation for what metric value the PodAutoscaler should attempt to maintain. Use with --scale-metric flag to configure the metric name for which the target value should be maintained. Default metric name is concurrency. The flag defaults to --concurrency-limit when given.
       --scale-utilization int             Percentage of concurrent requests utilization before scaling up. (default 70)
       --scale-window string               Duration to look back for making auto-scaling decisions. The service is scaled to zero if no request was received in during that time. (eg: 10s)
+      --security-context string           Predefined security context for the service. Accepted values: 'none' for no security context and 'strict' for dropping all capabilities, running as non-root, and no privilege escalation. (default "none")
       --service-account string            Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
       --tag strings                       Set tag (format: --tag revisionRef=tagName) where revisionRef can be a revision or '@latest' string representing latest ready revision. This flag can be specified multiple times.
       --target string                     Work on local directory instead of a remote cluster (experimental)
+      --timeout int                       Duration in seconds that the request routing layer will wait for a request delivered to a container to begin replying (default 300)
+      --toleration strings                Add toleration to be set, works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --tolerations Key="key1",Operator="Equal",Value="value1",Effect="NoSchedule"
       --traffic strings                   Set traffic distribution (format: --traffic revisionRef=percent) where revisionRef can be a revision or a tag or '@latest' string representing latest ready revision. This flag can be given multiple times with percent summing up to 100%.
       --untag strings                     Untag revision (format: --untag tagName). This flag can be specified multiple times.
       --user int                          The user ID to run the container (e.g., 1001).
-      --volume stringArray                Add a volume from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret: or sc:). Example: --volume myvolume=cm:myconfigmap or --volume myvolume=secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
+      --volume stringArray                Add a volume from a ConfigMap (prefix cm: or config-map:) a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:) or a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim). PersistentVolumeClaim only works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --volume myvolume=cm:myconfigmap, --volume myvolume=secret:mysecret or --volume emptyDir:myvol:size=1Gi,type=Memory. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
       --wait                              Wait for 'service update' operation to be completed. (default true)
       --wait-timeout int                  Seconds to wait before giving up on waiting for service to be ready. (default 600)
+      --wait-window int                   Seconds to wait for service to be ready after a false ready condition is returned (default 2)
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_service_wait.md

@@ -0,0 +1,48 @@
+## kn service wait
+
+Wait for a service to be ready
+
+```
+kn service wait NAME
+```
+
+### Examples
+
+```
+
+  # Waits on a service 'svc'
+  kn service wait svc
+
+  # Waits on a service 'svc' with a timeout
+  kn service wait svc --wait-timeout 10
+
+  # Waits on a service 'svc' with a timeout and wait window
+  kn service wait svc --wait-timeout 10 --wait-window 1
+```
+
+### Options
+
+```
+  -h, --help               help for wait
+  -n, --namespace string   Specify the namespace to operate in.
+      --wait-timeout int   Seconds to wait before giving up on waiting for service to be ready. (default 600)
+      --wait-window int    Seconds to wait for service to be ready after a false ready condition is returned (default 2)
+```
+
+### Options inherited from parent commands
+
+```
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
+```
+
+### SEE ALSO
+
+* [kn service](kn_service.md)	 - Manage Knative services
+

docs/cmd/kn_source.md

@@ -15,11 +15,14 @@ kn source SOURCE|COMMAND
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_apiserver.md

@@ -15,11 +15,14 @@ kn source apiserver COMMAND
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_apiserver_create.md

@@ -26,17 +26,20 @@ kn source apiserver create NAME --resource RESOURCE --sink SINK
       --resource stringArray      Specification for which events to listen, in the format Kind:APIVersion:LabelSelector, e.g. "Event:sourcesv1:key=value".
                                   "LabelSelector" is a list of comma separated key value pairs. "LabelSelector" can be omitted, e.g. "Event:sourcesv1".
       --service-account string    Name of the service account to use to run this source
-  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the current namespace. If referring to a Knative service in another namespace, 'ksvc:name:namespace' combination must be provided explicitly.
+  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace.
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_apiserver_delete.md

@@ -24,11 +24,14 @@ kn source apiserver delete NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_apiserver_describe.md

@@ -23,7 +23,7 @@ kn source apiserver describe NAME
       --allow-missing-template-keys   If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
   -h, --help                          help for describe
   -n, --namespace string              Specify the namespace to operate in.
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
   -v, --verbose                       More output.
@@ -32,11 +32,14 @@ kn source apiserver describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_apiserver_list.md

@@ -25,7 +25,7 @@ kn source apiserver list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -33,11 +33,14 @@ kn source apiserver list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_apiserver_update.md

@@ -26,17 +26,20 @@ kn source apiserver update NAME
       --resource stringArray      Specification for which events to listen, in the format Kind:APIVersion:LabelSelector, e.g. "Event:sourcesv1:key=value".
                                   "LabelSelector" is a list of comma separated key value pairs. "LabelSelector" can be omitted, e.g. "Event:sourcesv1".
       --service-account string    Name of the service account to use to run this source
-  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the current namespace. If referring to a Knative service in another namespace, 'ksvc:name:namespace' combination must be provided explicitly.
+  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace.
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_binding.md

@@ -15,11 +15,14 @@ kn source binding COMMAND
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_binding_create.md

@@ -20,18 +20,21 @@ kn source binding create NAME --subject SUBJECT --sink SINK
       --ce-override stringArray   Cloud Event overrides to apply before sending event to sink. Example: '--ce-override key=value' You may be provide this flag multiple times. To unset, append "-" to the key (e.g. --ce-override key-).
   -h, --help                      help for create
   -n, --namespace string          Specify the namespace to operate in.
-  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the current namespace. If referring to a Knative service in another namespace, 'ksvc:name:namespace' combination must be provided explicitly.
+  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace.
       --subject string            Subject which emits cloud events. This argument takes format kind:apiVersion:name for named resources or kind:apiVersion:labelKey1=value1,labelKey2=value2 for matching via a label selector
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_binding_delete.md

@@ -24,11 +24,14 @@ kn source binding delete NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_binding_describe.md

@@ -23,7 +23,7 @@ kn source binding describe NAME
       --allow-missing-template-keys   If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
   -h, --help                          help for describe
   -n, --namespace string              Specify the namespace to operate in.
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
   -v, --verbose                       More output.
@@ -32,11 +32,14 @@ kn source binding describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_binding_list.md

@@ -25,7 +25,7 @@ kn source binding list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -33,11 +33,14 @@ kn source binding list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_binding_update.md

@@ -20,18 +20,21 @@ kn source binding update NAME
       --ce-override stringArray   Cloud Event overrides to apply before sending event to sink. Example: '--ce-override key=value' You may be provide this flag multiple times. To unset, append "-" to the key (e.g. --ce-override key-).
   -h, --help                      help for update
   -n, --namespace string          Specify the namespace to operate in.
-  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the current namespace. If referring to a Knative service in another namespace, 'ksvc:name:namespace' combination must be provided explicitly.
+  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace.
       --subject string            Subject which emits cloud events. This argument takes format kind:apiVersion:name for named resources or kind:apiVersion:labelKey1=value1,labelKey2=value2 for matching via a label selector
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_container.md

@@ -15,11 +15,14 @@ kn source container create|delete|update|list|describe
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_container_create.md

@@ -17,35 +17,47 @@ kn source container create NAME --image IMAGE --sink SINK
 ### Options
 
 ```
-      --arg stringArray              Add argument to the container command. Example: --arg myArg1 --arg --myArg2 --arg myArg3=3. You can use this flag multiple times.
-      --cmd stringArray              Specify command to be used as entrypoint instead of default one. Example: --cmd /app/start or --cmd sh --cmd /app/start.sh or --cmd /app/start --arg myArg to pass additional arguments.
-      --containers string            Specify path to file including definition for additional containers, alternatively use '-' to read from stdin. Example: --containers ./containers.yaml or --containers -.
-  -e, --env stringArray              Environment variable to set. NAME=value; you may provide this flag any number of times to set multiple environment variables. To unset, specify the environment variable name followed by a "-" (e.g., NAME-).
-      --env-file string              Path to a file containing environment variables (e.g. --env-file=/home/knative/service1/env).
-      --env-from stringArray         Add environment variables from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret:). Example: --env-from cm:myconfigmap or --env-from secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --env-from cm:myconfigmap-.
-      --env-value-from stringArray   Add environment variable from a value of key in ConfigMap (prefix cm: or config-map:) or a Secret (prefix sc: or secret:). Example: --env-value-from NAME=cm:myconfigmap:key or --env-value-from NAME=secret:mysecret:key. You can use this flag multiple times. To unset a value from a ConfigMap/Secret key reference, append "-" to the key, e.g. --env-value-from ENV-.
-  -h, --help                         help for create
-      --image string                 Image to run.
-      --limit strings                The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
-      --mount stringArray            Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
-  -n, --namespace string             Specify the namespace to operate in.
-  -p, --port string                  The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
-      --pull-secret string           Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
-      --request strings              The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
-      --service-account string       Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
-  -s, --sink string                  Addressable sink for events. You can specify a broker, channel, Knative service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the current namespace. If referring to a Knative service in another namespace, 'ksvc:name:namespace' combination must be provided explicitly.
-      --user int                     The user ID to run the container (e.g., 1001).
-      --volume stringArray           Add a volume from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret: or sc:). Example: --volume myvolume=cm:myconfigmap or --volume myvolume=secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
+      --arg stringArray               Add argument to the container command. Example: --arg myArg1 --arg --myArg2 --arg myArg3=3. You can use this flag multiple times.
+      --cmd stringArray               Specify command to be used as entrypoint instead of default one. Example: --cmd /app/start or --cmd sh --cmd /app/start.sh or --cmd /app/start --arg myArg to pass additional arguments.
+      --containers string             Specify path to file including definition for additional containers, alternatively use '-' to read from stdin. Example: --containers ./containers.yaml or --containers -.
+  -e, --env stringArray               Environment variable to set. NAME=value; you may provide this flag any number of times to set multiple environment variables. To unset, specify the environment variable name followed by a "-" (e.g., NAME-).
+      --env-file string               Path to a file containing environment variables (e.g. --env-file=/home/knative/service1/env).
+      --env-from stringArray          Add environment variables from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret:). Example: --env-from cm:myconfigmap or --env-from secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --env-from cm:myconfigmap-.
+      --env-value-from stringArray    Add environment variable from a value of key in ConfigMap (prefix cm: or config-map:) or a Secret (prefix sc: or secret:). Example: --env-value-from NAME=cm:myconfigmap:key or --env-value-from NAME=secret:mysecret:key. You can use this flag multiple times. To unset a value from a ConfigMap/Secret key reference, append "-" to the key, e.g. --env-value-from ENV-.
+  -h, --help                          help for create
+      --image string                  Image to run.
+      --limit strings                 The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
+      --mount stringArray             Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:), a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim) or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, --mount /mydir=emptyDir:myvol or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can mount a volume with readOnly config (true | false) also. Example: --mount /mydir=ed:ed1:readOnly=true. You can specify a volume subpath by following the volume name with slash separated path. Example: --mount /mydir=cm:myconfigmap/subpath/to/be/mounted. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
+  -n, --namespace string              Specify the namespace to operate in.
+      --node-affinity strings         Add node affinity to be set - only works if the feature gate is enabled in Knative Serving feature flags configuration. When key, operator, values (whitespace separated) and weight are defined for a type, they will be appended in nodeSelectorTerms in case of Required clause, implying the terms will be ORed, and for Preferred clause, all of them will be added in preferredDuringSchedulingIgnoredDuringExecution. Example: --node-affinity Type="Required",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1 antarctica-west1" or --node-affinity Type="Preferred",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1",Weight="1"
+      --node-selector stringArray     Add node selector to be set, you may provide this flag any number of times to set multiple node selectors, works if feature flag is enabled in Knative Serving feature flags configuration. Example: --node-selector Disktype="ssd". To unset, specify the key name followed by a "-", example: --node-selector Disktype- .
+  -p, --port string                   The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
+      --probe-liveness string         Add liveness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-liveness-opts string    Add common options to liveness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --probe-readiness string        Add readiness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-readiness-opts string   Add common options to readiness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --pull-policy string            Image pull policy. Valid values (case insensitive): Always | Never | IfNotPresent
+      --pull-secret string            Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
+      --request strings               The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
+      --security-context string       Predefined security context for the service. Accepted values: 'none' for no security context and 'strict' for dropping all capabilities, running as non-root, and no privilege escalation. (default "none")
+      --service-account string        Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
+  -s, --sink string                   Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace.
+      --toleration strings            Add toleration to be set, works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --tolerations Key="key1",Operator="Equal",Value="value1",Effect="NoSchedule"
+      --user int                      The user ID to run the container (e.g., 1001).
+      --volume stringArray            Add a volume from a ConfigMap (prefix cm: or config-map:) a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:) or a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim). PersistentVolumeClaim only works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --volume myvolume=cm:myconfigmap, --volume myvolume=secret:mysecret or --volume emptyDir:myvol:size=1Gi,type=Memory. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_container_delete.md

@@ -24,11 +24,14 @@ kn source container delete NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_container_describe.md

@@ -25,11 +25,14 @@ kn source container describe NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_container_list.md

@@ -25,7 +25,7 @@ kn source container list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -33,11 +33,14 @@ kn source container list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_container_update.md

@@ -17,35 +17,47 @@ kn source container update NAME --image IMAGE
 ### Options
 
 ```
-      --arg stringArray              Add argument to the container command. Example: --arg myArg1 --arg --myArg2 --arg myArg3=3. You can use this flag multiple times.
-      --cmd stringArray              Specify command to be used as entrypoint instead of default one. Example: --cmd /app/start or --cmd sh --cmd /app/start.sh or --cmd /app/start --arg myArg to pass additional arguments.
-      --containers string            Specify path to file including definition for additional containers, alternatively use '-' to read from stdin. Example: --containers ./containers.yaml or --containers -.
-  -e, --env stringArray              Environment variable to set. NAME=value; you may provide this flag any number of times to set multiple environment variables. To unset, specify the environment variable name followed by a "-" (e.g., NAME-).
-      --env-file string              Path to a file containing environment variables (e.g. --env-file=/home/knative/service1/env).
-      --env-from stringArray         Add environment variables from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret:). Example: --env-from cm:myconfigmap or --env-from secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --env-from cm:myconfigmap-.
-      --env-value-from stringArray   Add environment variable from a value of key in ConfigMap (prefix cm: or config-map:) or a Secret (prefix sc: or secret:). Example: --env-value-from NAME=cm:myconfigmap:key or --env-value-from NAME=secret:mysecret:key. You can use this flag multiple times. To unset a value from a ConfigMap/Secret key reference, append "-" to the key, e.g. --env-value-from ENV-.
-  -h, --help                         help for update
-      --image string                 Image to run.
-      --limit strings                The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
-      --mount stringArray            Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
-  -n, --namespace string             Specify the namespace to operate in.
-  -p, --port string                  The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
-      --pull-secret string           Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
-      --request strings              The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
-      --service-account string       Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
-  -s, --sink string                  Addressable sink for events. You can specify a broker, channel, Knative service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the current namespace. If referring to a Knative service in another namespace, 'ksvc:name:namespace' combination must be provided explicitly.
-      --user int                     The user ID to run the container (e.g., 1001).
-      --volume stringArray           Add a volume from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret: or sc:). Example: --volume myvolume=cm:myconfigmap or --volume myvolume=secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
+      --arg stringArray               Add argument to the container command. Example: --arg myArg1 --arg --myArg2 --arg myArg3=3. You can use this flag multiple times.
+      --cmd stringArray               Specify command to be used as entrypoint instead of default one. Example: --cmd /app/start or --cmd sh --cmd /app/start.sh or --cmd /app/start --arg myArg to pass additional arguments.
+      --containers string             Specify path to file including definition for additional containers, alternatively use '-' to read from stdin. Example: --containers ./containers.yaml or --containers -.
+  -e, --env stringArray               Environment variable to set. NAME=value; you may provide this flag any number of times to set multiple environment variables. To unset, specify the environment variable name followed by a "-" (e.g., NAME-).
+      --env-file string               Path to a file containing environment variables (e.g. --env-file=/home/knative/service1/env).
+      --env-from stringArray          Add environment variables from a ConfigMap (prefix cm: or config-map:) or a Secret (prefix secret:). Example: --env-from cm:myconfigmap or --env-from secret:mysecret. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --env-from cm:myconfigmap-.
+      --env-value-from stringArray    Add environment variable from a value of key in ConfigMap (prefix cm: or config-map:) or a Secret (prefix sc: or secret:). Example: --env-value-from NAME=cm:myconfigmap:key or --env-value-from NAME=secret:mysecret:key. You can use this flag multiple times. To unset a value from a ConfigMap/Secret key reference, append "-" to the key, e.g. --env-value-from ENV-.
+  -h, --help                          help for update
+      --image string                  Image to run.
+      --limit strings                 The resource requirement limits for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource limit, append "-" to the resource name, e.g. '--limit memory-'.
+      --mount stringArray             Mount a ConfigMap (prefix cm: or config-map:), a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:), a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim) or an existing Volume (without any prefix) on the specified directory. Example: --mount /mydir=cm:myconfigmap, --mount /mydir=secret:mysecret, --mount /mydir=emptyDir:myvol or --mount /mydir=myvolume. When a configmap or a secret is specified, a corresponding volume is automatically generated. You can mount a volume with readOnly config (true | false) also. Example: --mount /mydir=ed:ed1:readOnly=true. You can specify a volume subpath by following the volume name with slash separated path. Example: --mount /mydir=cm:myconfigmap/subpath/to/be/mounted. You can use this flag multiple times. For unmounting a directory, append "-", e.g. --mount /mydir-, which also removes any auto-generated volume.
+  -n, --namespace string              Specify the namespace to operate in.
+      --node-affinity strings         Add node affinity to be set - only works if the feature gate is enabled in Knative Serving feature flags configuration. When key, operator, values (whitespace separated) and weight are defined for a type, they will be appended in nodeSelectorTerms in case of Required clause, implying the terms will be ORed, and for Preferred clause, all of them will be added in preferredDuringSchedulingIgnoredDuringExecution. Example: --node-affinity Type="Required",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1 antarctica-west1" or --node-affinity Type="Preferred",Key="topology.kubernetes.io/zone",Operator="In",Values="antarctica-east1",Weight="1"
+      --node-selector stringArray     Add node selector to be set, you may provide this flag any number of times to set multiple node selectors, works if feature flag is enabled in Knative Serving feature flags configuration. Example: --node-selector Disktype="ssd". To unset, specify the key name followed by a "-", example: --node-selector Disktype- .
+  -p, --port string                   The port where application listens on, in the format 'NAME:PORT', where 'NAME' is optional. Examples: '--port h2c:8080' , '--port 8080'.
+      --probe-liveness string         Add liveness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-liveness-opts string    Add common options to liveness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --probe-readiness string        Add readiness probe to Service deployment. Supported probe types are HTTGet, Exec and TCPSocket. Format: [http,https]:host:port:path, exec:cmd[,cmd,...], tcp:host:port.
+      --probe-readiness-opts string   Add common options to readiness probe. Common opts (comma separated, case insensitive): InitialDelaySeconds=<int_value>, FailureThreshold=<int_value>, SuccessThreshold=<int_value>, PeriodSeconds=<int_value>, TimeoutSeconds=<int_value>
+      --pull-policy string            Image pull policy. Valid values (case insensitive): Always | Never | IfNotPresent
+      --pull-secret string            Image pull secret to set. An empty argument ("") clears the pull secret. The referenced secret must exist in the service's namespace.
+      --request strings               The resource requirement requests for this Service. For example, 'cpu=100m,memory=256Mi'. You can use this flag multiple times. To unset a resource request, append "-" to the resource name, e.g. '--request cpu-'.
+      --security-context string       Predefined security context for the service. Accepted values: 'none' for no security context and 'strict' for dropping all capabilities, running as non-root, and no privilege escalation. (default "none")
+      --service-account string        Service account name to set. An empty argument ("") clears the service account. The referenced service account must exist in the service's namespace.
+  -s, --sink string                   Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace.
+      --toleration strings            Add toleration to be set, works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --tolerations Key="key1",Operator="Equal",Value="value1",Effect="NoSchedule"
+      --user int                      The user ID to run the container (e.g., 1001).
+      --volume stringArray            Add a volume from a ConfigMap (prefix cm: or config-map:) a Secret (prefix secret: or sc:), an EmptyDir (prefix ed: or emptyDir:) or a PersistentVolumeClaim (prefix pvc: or persistentVolumeClaim). PersistentVolumeClaim only works if the feature gate is enabled in Knative Serving feature flags configuration. Example: --volume myvolume=cm:myconfigmap, --volume myvolume=secret:mysecret or --volume emptyDir:myvol:size=1Gi,type=Memory. You can use this flag multiple times. To unset a ConfigMap/Secret reference, append "-" to the name, e.g. --volume myvolume-.
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_list-types.md

@@ -24,7 +24,7 @@ kn source list-types
   -h, --help                          help for list-types
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
 ```
@@ -32,11 +32,14 @@ kn source list-types
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_list.md

@@ -28,7 +28,7 @@ kn source list
   -h, --help                          help for list
   -n, --namespace string              Specify the namespace to operate in.
       --no-headers                    When using the default output format, don't print headers (default: print headers).
-  -o, --output string                 Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
+  -o, --output string                 Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
       --show-managed-fields           If true, keep the managedFields when printing objects in JSON or YAML format.
       --template string               Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
   -t, --type strings                  Filter list on given source type. This flag can be given multiple times.
@@ -37,11 +37,14 @@ kn source list
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_ping.md

@@ -15,11 +15,14 @@ kn source ping COMMAND
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_ping_create.md

@@ -23,17 +23,20 @@ kn source ping create NAME --sink SINK
   -h, --help                      help for create
   -n, --namespace string          Specify the namespace to operate in.
       --schedule string           Optional schedule specification in crontab format (e.g. '*/2 * * * *' for every two minutes. By default fire every minute.
-  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an URI with an 'http://' or 'https://' schema, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace. If a prefix is not provided, it is considered as a Knative service in the current namespace. If referring to a Knative service in another namespace, 'ksvc:name:namespace' combination must be provided explicitly.
+  -s, --sink string               Addressable sink for events. You can specify a broker, channel, Knative service, Kubernetes service or URI. Examples: '--sink broker:nest' for a broker 'nest', '--sink channel:pipe' for a channel 'pipe', '--sink ksvc:mysvc:mynamespace' for a Knative service 'mysvc' in another namespace 'mynamespace', '--sink https://event.receiver.uri' for an HTTP URI, '--sink ksvc:receiver' or simply '--sink receiver' for a Knative service 'receiver' in the current namespace, '--sink svc:receiver:mynamespace' for a Kubernetes service 'receiver' in the 'mynamespace' namespace, '--sink special.eventing.dev/v1alpha1/channels:pipe' for GroupVersionResource of v1alpha1 'pipe'. If a prefix is not provided, it is considered as a Knative service in the current namespace.
 ```
 
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO

docs/cmd/kn_source_ping_delete.md

@@ -24,11 +24,14 @@ kn source ping delete NAME
 ### Options inherited from parent commands
 
 ```
-      --cluster string      name of the kubeconfig cluster to use
-      --config string       kn configuration file (default: ~/.config/kn/config.yaml)
-      --context string      name of the kubeconfig context to use
-      --kubeconfig string   kubectl configuration file (default: ~/.kube/config)
-      --log-http            log http traffic
+      --as string              username to impersonate for the operation
+      --as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups
+      --as-uid string          uid to impersonate for the operation
+      --cluster string         name of the kubeconfig cluster to use
+      --config string          kn configuration file (default: ~/.config/kn/config.yaml)
+      --context string         name of the kubeconfig context to use
+      --kubeconfig string      kubectl configuration file (default: ~/.kube/config)
+      --log-http               log http traffic
 ```
 
 ### SEE ALSO