flagger
flagger copied to clipboard
fluxcd
Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
Bumps the ci group with 3 updates in the / directory: [sigstore/cosign-installer](https://github.com/sigstore/cosign-installer), [docker/build-push-action](https://github.com/docker/build-push-action) and [goreleaser/goreleaser-action](https://github.com/goreleaser/goreleaser-action). Updates `sigstore/cosign-installer` from 3.5.0 to 3.7.0 Release notes Sourced from sigstore/cosign-installer's releases. v3.7.0 What's Changed...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
This PR adds support for configuring additional labels for the deployment using `deploymentLabels` in `values.yaml`.
Adding configurable disableTls option for webhooks. This is useful in cases where the target service uses self-signed certificates, or you need to connect to an insecure service for testing purposes.
## Describe the feature When one uses an external metric provider for the metric templates, changing the secret can only be done by deleting and recreating the canary object, which...
So when I read https://github.com/fluxcd/flagger/blob/b6ac5e19aa7fa2949bbc8bf37a0f6c1e31b1745d/docs/gitbook/usage/how-it-works.md?plain=1#L116-L117 I thought that when adding this annotation flagger would now update canary and trigger rollout to primary deployment directly with the changes in the configmap/secret....
when i use flagger default metric server we want to default skip tls verify
Canary object right now accepts values lower than one (`1`) for `primaryScalerReplicas` counts. This results in Flagger keep trying to update primary HPA replica count, but failing. The validation is...
## Describe the feature What problem are you trying to solve? Recovery original resource after delete canary, make sure deployment replica is ready can accept traffic from service. ### Proposed...
## Describe the feature My development team at work uses flux/flagger for all of our deployments. The biggest problem we have is the fact that our application is a monolithic...
### Describe the bug Using a local kubernetes cluster via Docker Desktop and following the instruction process defined here - https://docs.flagger.app/install/flagger-install-on-kubernetes , along with a local LinkerD setup defined here...
