Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Helm release flagger to v1.24.1 #195

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

weaveworksbot
Copy link
Collaborator

This PR contains the following updates:

Package Update Change
flagger (source) minor 1.21.0 -> 1.24.1

Release Notes

fluxcd/flagger

v1.24.1

Compare Source

Release date: 2022-10-26

This release comes with a fix to Gloo routing when a custom service name id used.

In addition, the Gloo ingress end-to-end testing was updated to Gloo Helm chart v1.12.31.

Fixes:
  • fix(gloo): Use correct route table name in case service name was overwritten
    #​1300

v1.24.0

Compare Source

Release date: 2022-10-23

Starting with this version, the Flagger release artifacts are published to
GitHub Container Registry, and they are signed with Cosign and GitHub ODIC.

OCI artifacts:

  • ghcr.io/fluxcd/flagger:<version> multi-arch container images
  • ghcr.io/fluxcd/flagger-manifest:<version> Kubernetes manifests
  • ghcr.io/fluxcd/charts/flagger:<version> Helm charts

To verify an OCI artifact with Cosign:

export COSIGN_EXPERIMENTAL=1
cosign verify ghcr.io/fluxcd/flagger:1.24.0
cosign verify ghcr.io/fluxcd/flagger-manifests:1.24.0
cosign verify ghcr.io/fluxcd/charts/flagger:1.24.0

To deploy Flagger from its OCI artifacts the GitOps way,
please see the Flux installation guide.

Improvements:
  • docs: Add guide on how to install Flagger with Flux OCI
    #​1294
  • ci: Publish signed Helm charts and manifests to GHCR
    #​1293
  • ci: Sign release and containers with Cosign and GitHub OIDC
    #​1292
  • ci: Adjust GitHub workflow permissions
    #​1286
  • docs: Add link to Flux governance document
    #​1286

v1.23.0

Compare Source

Release date: 2022-10-20

This release comes with support for Slack bot token authentication.

Improvements:
  • alerts: Add support for Slack bot token authentication
    #​1270
  • loadtester: logCmdOutput to logger instead of stdout
    #​1267
  • helm: Add app.kubernetes.io/version label to chart
    #​1264
  • Update Go to 1.19
    #​1264
  • Update Kubernetes packages to v1.25.3
    #​1283
  • Bump Contour to v1.22 in e2e tests
    #​1282
Fixes:
  • gatewayapi: Fix reconciliation of nil hostnames
    #​1276
  • alerts: Include cluster name in all alerts
    #​1275

v1.22.2

Compare Source

Release date: 2022-08-29

This release fixes a bug related scaling up the canary deployment when a
reference to an autoscaler is specified.

Furthermore, it contains updates to packages used by the project, including
updates to Helm and grpc-health-probe used in the loadtester.

CVEs fixed (originating from dependencies):

Fixes:
  • If HPA is set, it uses HPA minReplicas when scaling up the canary
    #​1253
Improvements:
  • Release loadtester v0.23.0
    #​1246
  • Add target and script to keep crds in sync
    #​1254
  • docs: add knative support to roadmap
    #​1258
  • Update dependencies
    #​1259
  • Release loadtester v0.24.0
    #​1261

v1.22.1

Compare Source

Release date: 2022-08-01

This minor release fixes a bug related to the use of HPA v2beta2 and updates
the KEDA ScaledObject API to include MetricType for ScaleTriggers.

Furthermore, the project has been updated to use Go 1.18 and Alpine 3.16.

Fixes:
  • Update KEDA ScaledObject API to include MetricType for Triggers
    #​1241
  • Fix fallback logic for HPAv2 to v2beta2
    #​1242
Improvements:

v1.22.0

Compare Source

Release date: 2022-07-11

This release with support for KEDA ScaledObjects as an alternative to HPAs. Check the
tutorial to understand it's usage
with Flagger.

The .spec.service.appProtocol field can now be used to specify the appProtocol
of the services that Flagger generates.

In addition, a bug related to the Contour prometheus query for when service name is overwritten
along with a bug related to a Contour HTTPProxy annotations have been fixed.

Furthermore, the installation guide for Alibaba ServiceMesh has been updated.

Improvements:
  • feat: Add an optional appProtocol field to spec.service
    #​1185
  • Update Kubernetes packages to v1.24.1
    #​1208
  • charts: Add namespace parameter to parameters table
    #​1210
  • Introduce ScalerReconciler and refactor HPA reconciliation
    #​1211
  • e2e: Update providers and Kubernetes to v1.23
    #​1212
  • Add support for KEDA ScaledObjects as an auto scaler
    #​1216
  • include Contour retryOn in the sample canary
    #​1223
Fixes:
  • fix contour prom query for when service name is overwritten
    #​1204
  • fix contour httproxy annotations overwrite
    #​1205
  • Fix primary HPA label reconciliation
    #​1215
  • fix: add finalizers to canaries
    #​1219
  • typo: boostrap -> bootstrap
    #​1220
  • typo: controller
    #​1221
  • update guide for flagger on aliyun ASM
    #​1222
  • Reintroducing empty check for metric template references.
    #​1224

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@weaveworksbot weaveworksbot force-pushed the renovate/flagger-1.x branch from fc33501 to 0f23b2e Compare May 13, 2023 00:03
@weaveworksbot weaveworksbot force-pushed the renovate/flagger-1.x branch from 0f23b2e to 2a0a1b9 Compare July 15, 2023 00:03
@weaveworksbot weaveworksbot force-pushed the renovate/flagger-1.x branch from fa8d0f0 to 040c34f Compare March 9, 2024 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants