Release 0.30.0

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,98 @@
+---
+name: Bug report
+about: Problems and issues with code or docs
+title: ''
+labels: kind/bug
+assignees: ''
+
+---
+
+<!--
+
+Welcome to ingress-nginx!  For a smooth issue process, try to answer the following questions.
+Don't worry if they're not all applicable; just try to include what you can :-)
+
+If you need to include code snippets or logs, please put them in fenced code
+blocks.  If they're super-long, please use the details tag like
+<details><summary>super-long log</summary> lots of stuff </details>
+
+-->
+
+<!--
+
+IMPORTANT!!!
+
+Please complete the next sections or the issue will be closed.
+This questions are the first thing we need to know to understand the context.
+
+-->
+
+**NGINX Ingress controller version**:
+
+**Kubernetes version** (use `kubectl version`):
+
+**Environment**:
+
+- **Cloud provider or hardware configuration**:
+- **OS** (e.g. from /etc/os-release):
+- **Kernel** (e.g. `uname -a`):
+- **Install tools**:
+- **Others**:
+
+**What happened**:
+
+<!-- (please include exact error messages if you can) -->
+
+**What you expected to happen**:
+
+<!-- What do you think went wrong? -->
+
+**How to reproduce it**:
+<!---
+
+As minimally and precisely as possible. Keep in mind we do not have access to your cluster or application.
+Help up us (if possible) reproducing the issue using minikube or kind.
+
+## Install minikube/kind
+
+- Minikube https://minikube.sigs.k8s.io/docs/start/
+- Kind https://kind.sigs.k8s.io/docs/user/quick-start/
+
+## Install the ingress controller
+
+kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/baremetal/deploy.yaml
+
+## Install an application that will act as default backend (is just an echo app)
+
+kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/docs/examples/http-svc.yaml
+
+## Create an ingress (please add any additional annotation required)
+
+echo "
+  apiVersion: networking.k8s.io/v1beta1
+  kind: Ingress
+  metadata:
+    name: foo-bar
+  spec:
+    rules:
+    - host: foo.bar
+      http:
+        paths:
+        - backend:
+            serviceName: http-svc
+            servicePort: 80
+          path: /
+" | kubectl apply -f -
+
+## make a request
+
+POD_NAME=$(k get pods -n ingress-nginx -l app.kubernetes.io/name=ingress-nginx -o NAME)
+kubectl exec -it -n ingress-nginx $POD_NAME -- curl -H 'Host: foo.bar' localhost
+
+--->
+
+**Anything else we need to know**:
+
+<!-- If this is actually about documentation, add `/kind documentation` below -->
+
+/kind bug

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,30 @@
+---
+name: Feature request
+about: Suggest an idea for this project or its docs
+title: ''
+labels: kind/feature
+assignees: ''
+
+---
+
+<!--
+
+Welcome to ingress-nginx!  For a smooth feature request process, try to
+answer the following questions. Don't worry if they're not all applicable; just
+try to include what you can :-)
+
+If you need to include code snippets or logs, please put them in fenced code
+blocks.  If they're super-long, please use the details tag like
+<details><summary>super-long log</summary> lots of stuff </details>
+
+-->
+
+<!-- What do you want to happen? -->
+
+<!-- Is there currently another issue associated with this? -->
+
+<!-- Does it require a particular kubernetes version? -->
+
+<!-- If this is actually about documentation, add `/kind documentation` below -->
+
+/kind feature

.github/ISSUE_TEMPLATE/support-question.md

@@ -0,0 +1,37 @@
+---
+name: Question
+about: Any questions you might have.
+title: ''
+labels: triage/support
+assignees: ''
+
+---
+
+<!--
+
+Welcome to ingress-nginx!
+
+You probably didn't want to be one this page.  It shouldn't really be here anyway.
+
+* If you want a quick response to a question, ask on the Kubernetes Slack instance in #ingress-nginx.
+
+* If this is actually a bug or a feature request, file one of those.  If you're
+  not sure which, just take a guess and we can always re-label.
+
+* If you think this might turn into a bug or feature request, but you're not
+  sure, try asking in Slack first.
+
+-->
+
+<!--
+
+Still here?  Double-check that this hasn't been asked before, then put your question below
+with as many details as possible.
+
+If you need to include code snippets or logs, please put them in fenced code
+blocks.  If they're super-long, please use the details tag like
+<details><summary>super-long log</summary> lots of stuff </details>
+
+-->
+
+/triage support

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,10 +1,33 @@
-<!--  Thanks for sending a pull request!  Here are some tips for you:
-1. If this is your first time, read our contributor guidelines https://git.k8s.io/community/contributors/guide/pull-requests.md#the-pull-request-submit-process and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
-2. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
--->
+<!--- Provide a general summary of your changes in the Title above --->
+<!--- Please don't @-mention people in PR or commit messages (do so in an additional comment). --->
+
+## What this PR does / why we need it:
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## Types of changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
 
-**What this PR does / why we need it**:
+## Which issue/s this PR fixes
+<!--
+(optional, in `fixes #<issue number>` format, will close that issue when PR gets merged):
+
+fixes #
+-->
 
-**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
 
-**Special notes for your reviewer**:
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.
+- [ ] I've read the [CONTRIBUTION](https://github.com/kubernetes/ingress-nginx/blob/master/CONTRIBUTING.md) guide
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.

.github/actions/mkdocs/Dockerfile

@@ -0,0 +1,8 @@
+FROM squidfunk/mkdocs-material:5.2.3
+
+COPY action.sh /action.sh
+
+RUN apk add --no-cache bash \
+  && chmod +x /action.sh
+
+ENTRYPOINT ["/action.sh"]

.github/actions/mkdocs/action.sh

@@ -0,0 +1,51 @@
+#!/bin/bash
+
+# Copyright 2020 The Kubernetes 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.
+
+set -e
+
+REQUIREMENTS="${GITHUB_WORKSPACE}/requirements.txt"
+
+if [ -f "${REQUIREMENTS}" ]; then
+    pip install -r "${REQUIREMENTS}"
+fi
+
+if [ -n "${GITHUB_TOKEN}" ]; then
+    remote_repo="https://x-access-token:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git"
+elif [ -n "${PERSONAL_TOKEN}" ]; then
+    remote_repo="https://x-access-token:${PERSONAL_TOKEN}@github.com/${GITHUB_REPOSITORY}.git"
+fi
+
+git config --global user.name "$GITHUB_ACTOR"
+git config --global user.email "[email protected]"
+
+mkdocs build --config-file "${GITHUB_WORKSPACE}/mkdocs.yml"
+
+git clone --branch=gh-pages --depth=1 "${remote_repo}" gh-pages
+cd gh-pages
+
+# copy current index file index.yaml before any change
+temp_worktree=$(mktemp -d)
+cp --force "index.yaml" "$temp_worktree/index.yaml"
+# remove current content in branch gh-pages
+git rm -r .
+# copy new doc.
+cp -r ../site/* .
+# restore chart index
+cp "$temp_worktree/index.yaml" .
+# commit changes
+git add .
+git commit -m "Deploy GitHub Pages"
+git push --force --quiet "${remote_repo}" gh-pages > /dev/null 2>&1

.github/actions/mkdocs/action.yml

@@ -0,0 +1,9 @@
+# action.yml
+name: 'Deploy MkDocs'
+description: 'Deploys MkDocs site'
+branding:
+  icon: 'arrow-up-circle'
+  color: 'orange'
+runs:
+  using: 'docker'
+  image: 'Dockerfile'

.github/workflows/main.yaml

@@ -0,0 +1,37 @@
+name: Documentation and Helm chart
+
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+
+  docs:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout master
+        uses: actions/checkout@v1
+
+      - name: Deploy docs
+        uses: ./.github/actions/mkdocs
+        env:
+          PERSONAL_TOKEN: ${{ secrets.PERSONAL_TOKEN }}
+
+  chart:
+    needs: docs
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout master
+        uses: actions/checkout@v1
+
+      - name: Setup
+        shell: bash
+        run: |
+          git config --global user.name "$GITHUB_ACTOR"
+          git config --global user.email "[email protected]"
+
+      - name: Run chart-releaser
+        uses: helm/[email protected]
+        env:
+          CR_TOKEN: "${{ secrets.PERSONAL_TOKEN }}"