ying

Results 11 issues of ying

Fix of issue #1193 With the changes, we can see below "canary status" * succeed case ``` flagger-helloworld-demo-rollout Waiting 0 2022-05-16T08:01:31Z flagger-helloworld-demo-rollout Progressing 0 2022-05-16T08:02:31Z flagger-helloworld-demo-rollout Progressing 0 2022-05-16T08:03:31Z flagger-helloworld-demo-rollout...

## Describe the feature During promotion , flagger just copy the spec of deployment, and then start traffic routing & scale down canary But for some slow startup application, I...

## Describe the feature Flagger provides different kinds of webhooks to control the rollout process. Besides all current webhooks, per our business requirement, we hope to have a webhook between...

The documentation https://onsi.github.io/ginkgo/#writing-custom-reporters said: `RunSpecsWithDefaultAndCustomReporters` will run your custom reporters alongside Ginkgo’s default reporter. `RunSpecsWithCustomReporters` will only run the custom reporters you pass in. If you wish to run your...

waiting-for-response

The problem happens in release 0.17, but should not be a regression issue on 0.17. When creating knative application in a namespace in which limit range min/max specified, i.e. limit...

kind/bug
help wanted
area/API
good first issue
triage/accepted

This PR is used to resolve https://github.com/kedacore/keda/issues/3588 * use the existing Trigger.Name field as the scalerName * add scalerName to prometheus metric as a label to facilitate the grafana dashboard...

### Report We had multiple scaling metrics with azure-data-explorer-scaler when the metric extracted from the same azure-data-explorer-db, but from different query. i.e I created a trigger using metricName "metric-A" to...

bug

We are hosting argo-rollout dashboard as an application for monitoring purpose. **Problem:** Per security compliance, we don't want people to execute any action through the dashboard manually. We edited the...

duplicate
enhancement
dashboard
hacktoberfest

### Description with the latest https://docs.docker.com/desktop/release-notes/#4250 4.25.0 release, our application running on the local Kubernetes can't access external website anymore. The coredns pods kept failing with ``` [ERROR] plugin/errors: 2...

status/triage
area/Kube
version/4.25.0

When playing with Cloud object storage service, its credential looks like: ``` { "apikey": "xxxxx", "cos_hmac_keys": { "access_key_id": "xxxx", "secret_access_key": "xxxx" }, "endpoints": "https://control.cloud-object-storage.cloud.ibm.com/v2/endpoints", "iam_apikey_description": "xxxx", "iam_apikey_name": "test-cos-crendentail", "iam_role_crn": "xxxx",...

enhancement