use latest tag from triggermesh-core

Author: odacremolbap

.github/workflows/release.yaml

@@ -29,7 +29,7 @@ jobs:
           find ./config/3*.yaml -exec cat {} \; -exec echo \; -exec echo --- \; -exec echo \; >> ./releases/manifests/triggermesh-core-crds.yaml
           find ./config/configmaps/*.yaml -exec cat {} \; -exec echo \; -exec echo --- \; -exec echo \; >> ./releases/manifests/triggermesh-core.yaml
           TAG=${GITHUB_REF#refs/*/}
-          sed -e 's/:dev/:'"$TAG"'/g' -e 's#ko://github.com/triggermesh/triggermesh-core/cmd/core-controller#gcr.io/triggermesh/triggermesh-core:'"$TAG"'#g' ./config/5*.yaml >> ./releases/manifests/triggermesh-core.yaml
+          sed -e 's/:latest/:'"$TAG"'/g' -e 's#ko://github.com/triggermesh/triggermesh-core/cmd/core-controller#gcr.io/triggermesh/triggermesh-core:'"$TAG"'#g' ./config/5*.yaml >> ./releases/manifests/triggermesh-core.yaml
 
       - name: Run GoReleaser
         uses: goreleaser/goreleaser-action@v4

config/500-core-controller.yaml

@@ -67,11 +67,11 @@ spec:
           value: triggermesh.io
         # Deployment images
         - name: MEMORYBROKER_BROKER_IMAGE
-          value: gcr.io/triggermesh/memory-broker:dev
+          value: gcr.io/triggermesh/memory-broker:latest
         - name: REDISBROKER_REDIS_IMAGE
           value: redis/redis-stack-server:latest
         - name: REDISBROKER_BROKER_IMAGE
-          value: gcr.io/triggermesh/redis-broker:dev
+          value: gcr.io/triggermesh/redis-broker:latest
         # Pull policy for broker, REMOVE for production environments
         - name: REDISBROKER_BROKER_IMAGE_PULL_POLICY
           value: Always

docs/CONTRIBUTING.md

@@ -14,22 +14,24 @@ We define _contributions_ as:
 
 ## Contents
 
-1. [Code of Conduct](#code-of-conduct)
-
-1. [Submitting Contributions](#submitting-contributions)
-   - [Reporting Bugs](#reporting-bugs)
-   - [Requesting Features and Enhancements](#requesting-features-and-enhancements)
-   - [Submitting Code Changes](#submitting-code-changes)
-
-1. [Development Guidelines](#development-guidelines)
-
-   1. [Prerequisites](#prerequisites)
+- [Contributing to TriggerMesh](#contributing-to-triggermesh)
+  - [Contents](#contents)
+  - [Code of Conduct](#code-of-conduct)
+  - [Submitting Contributions](#submitting-contributions)
+    - [Reporting Bugs](#reporting-bugs)
+      - [Issue Description](#issue-description)
+      - [Code Styling](#code-styling)
+    - [Requesting Features and Enhancements](#requesting-features-and-enhancements)
+    - [Submitting Code Changes](#submitting-code-changes)
+  - [Development Guidelines](#development-guidelines)
+    - [Prerequisites](#prerequisites)
       - [Go Toolchain](#go-toolchain)
       - [Kubernetes](#kubernetes)
       - [ko](#ko)
-
-   1. [Running the Controller](#running-the-controller)
+    - [Running the Controller](#running-the-controller)
       - [Controller Configuration](#controller-configuration)
+        - [Configuration Read From the Environment](#configuration-read-from-the-environment)
+        - [Configuration Read From ConfigMaps](#configuration-read-from-configmaps)
       - [Locally](#locally)
 
 ## Code of Conduct
@@ -250,13 +252,6 @@ Additionally, the desired build version (container image) of each TriggerMesh co
 environment variables. The full list can be found inside the [controller's Deployment manifest][tm-allenvs]. By default,
 the controller uses the latest tagged public image from `gcr.io/triggermesh` for any given component.
 
-To use your own image instead (e.g. the result of a development build), simply set the corresponding environment
-variable to the reference of the image to use. For example:
-
-```sh
-# Use a custom build of the "Zendesk" event source adapter.
-export ZENDESKSOURCE_IMAGE=docker.io/myuser/zendesksource:devel
-```
 
 ##### Configuration Read From ConfigMaps