Merge branch 'master' of github.com:argoproj/argo-rollouts into chore…

…-bump-k8s-dep

Signed-off-by: zachaller <[email protected]>

.github/workflows/go.yml

@@ -90,7 +90,7 @@ jobs:
           path: coverage.out
 
       - name: Upload code coverage information to codecov.io
-        uses: codecov/[email protected].2
+        uses: codecov/[email protected].3
         with:
           file: coverage.out
 

Makefile

@@ -225,7 +225,7 @@ test-e2e: install-devtools-local
 
 .PHONY: test-unit
  test-unit: install-devtools-local
-	${DIST_DIR}/gotestsum --junitfile=junit.xml --format=testname -- -covermode=count -coverprofile=coverage.out `go list ./... | grep -v ./test/cmd/sample-metrics-plugin`
+	${DIST_DIR}/gotestsum --junitfile=junit.xml --format=testname -- -covermode=count -coverprofile=coverage.out `go list ./... | grep -v ./test/cmd/metrics-plugin-sample`
 
 
 .PHONY: coverage
@@ -284,9 +284,9 @@ checksums:
 # https://www.jetbrains.com/help/go/attach-to-running-go-processes-with-debugger.html
 .PHONY: build-sample-metric-plugin-debug
 build-sample-metric-plugin-debug:
-	go build -gcflags="all=-N -l" -o metric-plugin test/cmd/sample-metrics-plugin/main.go
+	go build -gcflags="all=-N -l" -o metric-plugin test/cmd/metrics-plugin-sample/main.go
 
 .PHONY: build-sample-traffic-plugin-debug
 build-sample-traffic-plugin-debug:
-	go build -gcflags="all=-N -l" -o traffic-plugin test/cmd/sample-trafficrouter-plugin/main.go
+	go build -gcflags="all=-N -l" -o traffic-plugin test/cmd/trafficrouter-plugin-sample/main.go
 

USERS.md

@@ -11,6 +11,7 @@ Organizations below are **officially** using Argo Rollouts. Please send a PR wit
 1. [Calm](https://www.calm.com/)
 1. [Codefresh](https://codefresh.io/)
 1. [Credit Karma](https://creditkarma.com/)
+1. [DaoCloud](https://daocloud.io)
 1. [Databricks](https://github.com/databricks)
 1. [Devtron Labs](https://github.com/devtron-labs/devtron)
 1. [Farfetch](https://www.farfetch.com/)

docs/analysis/datadog.md

@@ -40,10 +40,10 @@ kind: Secret
 metadata:
   name: datadog
 type: Opaque
-data:
+stringData:
   address: https://api.datadoghq.com
   api-key: <datadog-api-key>
   app-key: <datadog-app-key>
 ```
 
-`apiVersion` here is different from the `apiVersion` from the Datadog configuration above.
+`apiVersion` here is different from the `apiVersion` from the Datadog configuration above.

docs/analysis/influxdb.md

@@ -34,7 +34,7 @@ kind: Secret
 metadata:
   name: influxdb
 type: Opaque
-data:
+stringData:
   address: <infuxdb-url>
   authToken: <influxdb-auth-token>
   org: <influxdb-org>

docs/analysis/newrelic.md

@@ -33,7 +33,7 @@ kind: Secret
 metadata:
   name: newrelic
 type: Opaque
-data:
+stringData:
   personal-api-key: <newrelic-personal-api-key>
   account-id: <newrelic-account-id>
   region: "us" # optional, defaults to "us" if not set. Only set to "eu" if you use EU New Relic
@@ -47,7 +47,7 @@ kind: Secret
 metadata:
   name: newrelic
 type: Opaque
-data:
+stringData:
   personal-api-key: <newrelic-personal-api-key>
   account-id: <newrelic-account-id>
   region: "us" # optional, defaults to "us" if not set. Only set to "eu" if you use EU New Relic

docs/analysis/plugins.md

@@ -2,10 +2,10 @@
 
 !!! important Available since v1.5 - Status: Alpha
 
-Argo Rollouts supports getting analysis metrics via 3rd party plugin system. This allows users to extend the capabilities of Rollouts 
+Argo Rollouts supports getting analysis metrics via 3rd party plugin system. This allows users to extend the capabilities of Rollouts
 to support metric providers that are not natively supported. Rollout's uses a plugin library called
-[go-plugin](https://github.com/hashicorp/go-plugin) to do this. You can find a sample plugin 
-here: [rollouts-sample_prometheus-metric-plugin](https://github.com/argoproj-labs/rollouts-sample_prometheus-metric-plugin)
+[go-plugin](https://github.com/hashicorp/go-plugin) to do this. You can find a sample plugin
+here: [rollouts-plugin-metric-sample-prometheus](https://github.com/argoproj-labs/rollouts-plugin-metric-sample-prometheus)
 
 ## Using a Metric Plugin
 
@@ -36,7 +36,7 @@ data:
 
 ### Using a HTTP(S) server to host the plugin executable
 
-Argo Rollouts supports downloading the plugin executable from a HTTP(S) server. To use this method, you will need to 
+Argo Rollouts supports downloading the plugin executable from a HTTP(S) server. To use this method, you will need to
 configure the controller via the `argo-rollouts-config` configmap and set `pluginLocation` to a http(s) url. Example:
 
 ```yaml
@@ -47,7 +47,7 @@ metadata:
 data:
   metricProviderPlugins: |-
     - name: "argoproj-labs/sample-prometheus" # name of the plugin, it must match the name required by the plugin so it can find it's configuration
-      location: "https://github.com/argoproj-labs/rollouts-sample_prometheus-metric-plugin/releases/download/v0.0.4/metric-plugin-linux-amd64" # supports http(s):// urls and file://
+      location: "https://github.com/argoproj-labs/rollouts-plugin-metric-sample-prometheus/releases/download/v0.0.4/metric-plugin-linux-amd64" # supports http(s):// urls and file://
       sha256: "dac10cbf57633c9832a17f8c27d2ca34aa97dd3d" #optional sha256 checksum of the plugin executable
 ```
 
@@ -56,18 +56,18 @@ data:
 Depending on which method you use to install and the plugin, there are some things to be aware of.
 The rollouts controller will not start if it can not download or find the plugin executable. This means that if you are using
 a method of installation that requires a download of the plugin and the server hosting the plugin for some reason is not available and the rollouts
-controllers pod got deleted while the server was down or is coming up for the first time, it will not be able to start until 
+controllers pod got deleted while the server was down or is coming up for the first time, it will not be able to start until
 the server hosting the plugin is available again.
 
 Argo Rollouts will download the plugin at startup only once but if the pod is deleted it will need to download the plugin again on next startup. Running
 Argo Rollouts in HA mode can help a little with this situation because each pod will download the plugin at startup. So if a single pod gets
-deleted during a server outage, the other pods will still be able to take over because there will already be a plugin executable available to it. It is the 
+deleted during a server outage, the other pods will still be able to take over because there will already be a plugin executable available to it. It is the
 responsibility of the Argo Rollouts administrator to define the plugin installation method considering the risks of each approach.
 
 ## List of Available Plugins (alphabetical order)
 
 #### Add Your Plugin Here
   * If you have created a plugin, please submit a PR to add it to this list.
-#### [rollouts-sample_prometheus-metric-plugin](https://github.com/argoproj-labs/rollouts-sample_prometheus-metric-plugin)
-  * This is just a sample plugin that can be used as a starting point for creating your own plugin. 
+#### [rollouts-plugin-metric-sample-prometheus](https://github.com/argoproj-labs/rollouts-plugin-metric-sample-prometheus)
+  * This is just a sample plugin that can be used as a starting point for creating your own plugin.
 It is not meant to be used in production. It is based on the built-in prometheus provider.

docs/analysis/wavefront.md

@@ -35,7 +35,7 @@ kind: Secret
 metadata:
   name: wavefront-api-tokens
 type: Opaque
-data:
+stringData:
   example1.wavefront.com: <token1>
   example2.wavefront.com: <token2>
 ```

docs/features/traffic-management/plugins.md

@@ -5,7 +5,7 @@
 Argo Rollouts supports getting analysis metrics via 3rd party plugin system. This allows users to extend the capabilities of Rollouts
 to support metric providers that are not natively supported. Rollout's uses a plugin library called
 [go-plugin](https://github.com/hashicorp/go-plugin) to do this. You can find a sample plugin
-here: [rollouts-sample_nginx-trafficrouter-plugin](https://github.com/argoproj-labs/rollouts-sample_nginx-trafficrouter-plugin)
+here: [rollouts-plugin-trafficrouter-sample-nginx](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-sample-nginx)
 
 ## Using a Traffic Router Plugin
 
@@ -47,7 +47,7 @@ metadata:
 data:
   trafficRouterPlugins: |-
     - name: "argoproj-labs/sample-nginx" # name of the plugin, it must match the name required by the plugin so it can find it's configuration
-      location: "https://github.com/argoproj-labs/rollouts-sample_nginx-trafficrouter-plugin/releases/download/v0.0.1/metric-plugin-linux-amd64" # supports http(s):// urls and file://
+      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-sample-nginx/releases/download/v0.0.1/metric-plugin-linux-amd64" # supports http(s):// urls and file://
       sha256: "08f588b1c799a37bbe8d0fc74cc1b1492dd70b2c" #optional sha256 checksum of the plugin executable
 ```
 
@@ -68,6 +68,9 @@ responsibility of the Argo Rollouts administrator to define the plugin installat
 
 #### Add Your Plugin Here
 * If you have created a plugin, please submit a PR to add it to this list.
-#### [rollouts-sample_nginx-trafficrouter-plugin](https://github.com/argoproj-labs/rollouts-sample_nginx-trafficrouter-plugin)
+#### [rollouts-plugin-trafficrouter-sample-nginx](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-sample-nginx)
 * This is just a sample plugin that can be used as a starting point for creating your own plugin.
   It is not meant to be used in production. It is based on the built-in prometheus provider.
+
+#### [rollouts-plugin-trafficrouter-contour](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-contour)
+* This is a plugin for support Contour.

docs/plugins.md

@@ -2,7 +2,7 @@
 
 ## High Level Overview
 
-Argo Rollouts plugins depend on hashicorp's [go-plugin](https://github.com/hashicorp/go-plugin) library. This library 
+Argo Rollouts plugins depend on hashicorp's [go-plugin](https://github.com/hashicorp/go-plugin) library. This library
 provides a way for a plugin to be compiled as a standalone executable and then loaded by the rollouts controller at runtime.
 This works by having the plugin executable act as a rpc server and the rollouts controller act as a client. The plugin executable
 is started by the rollouts controller and is a long-lived process and that the rollouts controller connects to over a unix socket.
@@ -11,22 +11,22 @@ The communication protocol uses golang built in net/rpc library so plugins have
 ## Plugin Repository
 
 In order to get plugins listed in the main argo rollouts documentation we ask that the plugin repository be created under
-the [argoproj-labs](https://github.com/argoproj-labs) organization. Please open an issue under argo-rollouts requesting a 
-repo which you would be granted admin access on. 
+the [argoproj-labs](https://github.com/argoproj-labs) organization. Please open an issue under argo-rollouts requesting a
+repo which you would be granted admin access on.
 
-There is also a standard naming convention for plugin names used for configmap registration, as well as what the plugin 
-uses for locating its specific configuration on rollout or analysis resources. The name needs to be in the form of 
-`<namespace>/<name>` and both <namespace> and <name> have a regular expression check that matches Github's requirements 
-for `username/org` and `repository name`. This requirement is in place to help with allowing multiple creators of the same plugin 
-types to exist such as `<org1>/nginx` and `<org2>/nginx`. These names could be based of the repo name such 
-as `argoproj-labs/rollouts-sample_prometheus-metric-plugin` but it is not a requirement. 
+There is also a standard naming convention for plugin names used for configmap registration, as well as what the plugin
+uses for locating its specific configuration on rollout or analysis resources. The name needs to be in the form of
+`<namespace>/<name>` and both <namespace> and <name> have a regular expression check that matches Github's requirements
+for `username/org` and `repository name`. This requirement is in place to help with allowing multiple creators of the same plugin
+types to exist such as `<org1>/nginx` and `<org2>/nginx`. These names could be based of the repo name such
+as `argoproj-labs/rollouts-plugin-metric-sample-prometheus` but it is not a requirement.
 
-There will also be a standard for naming repositories under argoproj-labs in the form of `rollouts-<tool>-<type>-plugin`
+There will also be a standard for naming repositories under argoproj-labs in the form of `rollouts-plugin-<type>-<tool>`
 where `<type>` is say `metric`, or `trafficrouter` and `<tool>` is the software the plugin is for say nginx.
 
 ## Plugin Name
 
-So now that we have an idea on plugin naming and repository standards let's pick a name to use for the rest of this 
+So now that we have an idea on plugin naming and repository standards let's pick a name to use for the rest of this
 documentation and call our plugin `argoproj-labs/nginx`.
 
 This name will be used in a few different spots the first is the config map that your plugin users will need to configure.
@@ -134,22 +134,22 @@ type TrafficRouterPlugin interface {
 
 ## Plugin Init Function
 
-Each plugin interface has a `InitPlugin` function, this function is called when the plugin is first started up and is only called 
-once per startup. The `InitPlugin` function is used as a means to initialize the plugin it gives you the plugin author the ability 
-to either set up a client for a specific metrics provider or in the case of a traffic router construct a client or informer 
+Each plugin interface has a `InitPlugin` function, this function is called when the plugin is first started up and is only called
+once per startup. The `InitPlugin` function is used as a means to initialize the plugin it gives you the plugin author the ability
+to either set up a client for a specific metrics provider or in the case of a traffic router construct a client or informer
 for kubernetes api. The one thing to note about this though is because these calls happen over RPC the plugin author should
 not depend on state being stored in the plugin struct as it will not be persisted between calls.
 
 ## Kubernetes RBAC
 
 The plugin runs as a child process of the rollouts controller and as such it will inherit the same RBAC permissions as the
-controller. This means that the service account for the rollouts controller will need the correct permissions for the plugin 
-to function. This might mean instructing users to create a role and role binding to the standard rollouts service account 
+controller. This means that the service account for the rollouts controller will need the correct permissions for the plugin
+to function. This might mean instructing users to create a role and role binding to the standard rollouts service account
 for the plugin to use. This will probably affect traffic router plugins more than metrics plugins.
 
 ## Sample Plugins
 
 There are two sample plugins within the argo-rollouts repo that you can use as a reference for creating your own plugin.
 
-* [Sample Metrics Plugin](https://github.com/argoproj/argo-rollouts/tree/master/test/cmd/sample-metrics-plugin)
-* [Sample Traffic Router Plugin](https://github.com/argoproj/argo-rollouts/tree/master/test/cmd/sample-trafficrouter-plugin)
+* [Metrics Plugin Sample](https://github.com/argoproj/argo-rollouts/tree/master/test/cmd/metrics-plugin-sample)
+* [Traffic Router Plugin Sample](https://github.com/argoproj/argo-rollouts/tree/master/test/cmd/trafficrouter-plugin-sample)

go.mod

@@ -6,10 +6,10 @@ require (
 	github.com/antonmedv/expr v1.12.5
 	github.com/argoproj/notifications-engine v0.4.0
 	github.com/argoproj/pkg v0.13.6
-	github.com/aws/aws-sdk-go-v2 v1.17.8
+	github.com/aws/aws-sdk-go-v2 v1.18.0
 	github.com/aws/aws-sdk-go-v2/config v1.18.21
 	github.com/aws/aws-sdk-go-v2/service/cloudwatch v1.25.9
-	github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2 v1.19.9
+	github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2 v1.19.10
 	github.com/blang/semver v3.5.1+incompatible
 	github.com/bombsimon/logrusr/v4 v4.0.0
 	github.com/evanphx/json-patch/v5 v5.6.0
@@ -24,7 +24,7 @@ require (
 	github.com/mitchellh/mapstructure v1.5.0
 	github.com/newrelic/newrelic-client-go v1.1.0
 	github.com/pkg/errors v0.9.1
-	github.com/prometheus/client_golang v1.14.0
+	github.com/prometheus/client_golang v1.15.0
 	github.com/prometheus/client_model v0.3.0
 	github.com/prometheus/common v0.42.0
 	github.com/prometheus/common/sigv4 v0.1.0
@@ -71,7 +71,7 @@ require (
 	github.com/google/go-github/v41 v41.0.0 // indirect
 	github.com/google/go-github/v45 v45.2.0 // indirect
 	github.com/matryer/is v1.4.0 // indirect
-	github.com/russross/blackfriday v1.5.2 // indirect
+	github.com/russross/blackfriday v1.6.0 // indirect
 )
 
 require (
@@ -84,8 +84,8 @@ require (
 	github.com/aws/aws-sdk-go v1.44.116 // indirect
 	github.com/aws/aws-sdk-go-v2/credentials v1.13.20 // indirect
 	github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.13.2 // indirect
-	github.com/aws/aws-sdk-go-v2/internal/configsources v1.1.32 // indirect
-	github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.4.26 // indirect
+	github.com/aws/aws-sdk-go-v2/internal/configsources v1.1.33 // indirect
+	github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.4.27 // indirect
 	github.com/aws/aws-sdk-go-v2/internal/ini v1.3.33 // indirect
 	github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.9.26 // indirect
 	github.com/aws/aws-sdk-go-v2/service/sso v1.12.8 // indirect
@@ -114,7 +114,7 @@ require (
 	github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da // indirect
 	github.com/google/btree v1.1.2 // indirect
 	github.com/google/gnostic v0.6.9 // indirect
-	github.com/google/go-cmp v0.5.9 // indirect
+	github.com/google/go-cmp v0.5.9
 	github.com/google/go-querystring v1.1.0 // indirect
 	github.com/google/gofuzz v1.2.0 // indirect
 	github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510 // indirect
@@ -157,7 +157,7 @@ require (
 	github.com/opsgenie/opsgenie-go-sdk-v2 v1.2.13 // indirect
 	github.com/peterbourgon/diskv v2.0.1+incompatible // indirect
 	github.com/pmezard/go-difflib v1.0.0 // indirect
-	github.com/prometheus/procfs v0.8.0 // indirect
+	github.com/prometheus/procfs v0.9.0 // indirect
 	github.com/slack-go/slack v0.12.1 // indirect
 	github.com/spf13/pflag v1.0.5 // indirect
 	github.com/stretchr/objx v0.5.0 // indirect