massdriver-0.0.29

Summary of Changes

• New images for massdriver and massdriver-ui

PRs

• bump image versions by @chrisghill in #43

Full Changelog: massdriver-0.0.28...massdriver-0.0.29

massdriver-0.0.28

Summary of Changes

• Bump image versions of massdriver (fixes bug in AWS cost reporting)

PRs

• Bump massdriver image to 1.5.1 by @chrisghill in #42

Full Changelog: massdriver-0.0.27...massdriver-0.0.28

massdriver-0.0.27

Summary of Changes

• Bump image versions of massdriver, massdriver-ui, and launch-control (patching vulnerabilities)
• Support Okta as an OIDC provider
• Move massdriver-ui healthcheck to be _health (consistent w/ massdriver)

PRs

• Massdriver/0.0.27 by @chrisghill in #41

Full Changelog: massdriver-0.0.26...massdriver-0.0.27

massdriver-0.0.26

Helm chart for deploying Massdriver

massdriver-0.0.25

Summary of Changes

• Fixed the issue with the artifactgc job failing due to RBAC
• Bumped image versions of Massdriver, UI and Launch-Control

The finalizer issue may have left numerous pods and old workflows around. The pods are meant to clean up Argo artifacts (not to be confused with Massdriver artifacts). This also prevented workflows from being deleted due to a finalizer on the workflow requiring the cleanup job to execute successfully. This issue should be fixed now. However, this won't clean up existing pods and workflows, it only fixes the issue going forward. To clean up old workflows, you can run the following command to remove the finalizer, allowing the workflow to be deleted:

kubectl get workflows -n massdriver -o name | xargs -P 10 -I {} kubectl patch {} -n massdriver --type=json -p '[{"op
": "remove", "path": "/metadata/finalizers"}]'

You can also run the following command to clean up failed artifactgc jobs:

kubectl get pods -n massdriver | grep Error | awk '{print $1}' | xargs kubectl delete pod

PRs

• Create and bind role for Argo artifact GC by @chrisghill in #39

Full Changelog: massdriver-0.0.24...massdriver-0.0.25

massdriver-0.0.24

Summary of Changes

• Expose additional configurations for customizing OIDC buttons (label and icon).
• Add dev subdomain to PHX for testing purposes

PRs

• expose uiLabel and uiIconUrl for OIDC buttons by @chrisghill in #37
• Add 'dev' subdomain to PHX origin envs by @chrisghill in #38

Full Changelog: massdriver-0.0.23...massdriver-0.0.24

massdriver-0.0.23

Helm chart for deploying Massdriver

massdriver-0.0.22

Summary of Changes

• Updated massdriver and massdriver-ui image tags. These new images support SCIM integration for user management.

PRs What's Changed

• bump massdriver and UI versions by @chrisghill in #35

Full Changelog: massdriver-0.0.21...massdriver-0.0.22

massdriver-0.0.21

Helm chart for deploying Massdriver

Summary of Changes

• Adds extraEnvs and extraSecrets configuration options to inject custom environment variables into the Massdriver deployment
• Introduces Gateway API HTTPRoute support with configurable parent Gateway references
• Changes the default ingress.enabled value from true to false - users now can "opt-in" to either ingress or gateway API access

Breaking Changes

• Since ingress.enabled now defaults to false, this may disable the ingress in releases if it wasn't set to true in your local values overrides. However, if you are began by using the values-example.yaml, this automatically sets ingress.enabled to true.

PRs

• Add HTTPRoute config for GatewayAPI, and extraEnvs/extraSecrets by @chrisghill in #33

Full Changelog: massdriver-0.0.20...massdriver-0.0.21

massdriver-0.0.20

Helm chart for deploying Massdriver