Prepare for 4.27.1 (#9885)

.github/workflows/dogfood-deploy.yml

@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
     inputs:
       DOCKER_IMAGE:
-        description: 'The full name of the docker image to be deployed. (e.g. fleetdm/fleet:v4.27.0)'
+        description: 'The full name of the docker image to be deployed. (e.g. fleetdm/fleet:v4.27.1)'
         required: true
 
 # This allows a subsequently queued workflow run to interrupt previous runs

CHANGELOG.md

@@ -1,3 +1,9 @@
+## Fleet 4.27.1 (Feb 16, 2023)
+
+* Fixed "Turn off MDM" button appearing on host details without Fleet MDM enabled. 
+
+* Upgrade Go to 1.19.6 to remediate some low severity [denial of service vulnerabilities](https://groups.google.com/g/golang-announce/c/V0aBFqaFs_E/m/CnYKgKwBBQAJ) in the standard library.
+
 ## Fleet 4.27.0 (Feb 3, 2023)
 
 * Added API endpoint to unenroll a host from Fleet's MDM.

charts/fleet/Chart.yaml

@@ -8,4 +8,4 @@ version: v5.0.0
 home: https://github.com/fleetdm/fleet
 sources:
   - https://github.com/fleetdm/fleet.git
-appVersion: v4.27.0
+appVersion: v4.27.1

charts/fleet/values.yaml

@@ -2,7 +2,7 @@
 # All settings related to how Fleet is deployed in Kubernetes
 hostName: fleet.localhost
 replicas: 3 # The number of Fleet instances to deploy
-imageTag: v4.27.0 # Version of Fleet to deploy
+imageTag: v4.27.1 # Version of Fleet to deploy
 podAnnotations: {} # Additional annotations to add to the Fleet pod
 serviceAccountAnnotations: {} # Additional annotations to add to the Fleet service account
 resources:

docs/Deploying/Server-Installation.md

@@ -264,7 +264,7 @@ spec:
     spec:
       containers:
       - name: fleet
-        image: fleetdm/fleet:4.27.0
+        image: fleetdm/fleet:4.27.1
         env:
           # if running Fleet behind external ingress controller that terminates TLS
           - name: FLEET_SERVER_TLS

infrastructure/dogfood/terraform/aws/variables.tf

@@ -56,7 +56,7 @@ variable "database_name" {
 
 variable "fleet_image" {
   description = "the name of the container image to run"
-  default     = "fleetdm/fleet:v4.27.0"
+  default     = "fleetdm/fleet:v4.27.1"
 }
 
 variable "software_inventory" {

infrastructure/dogfood/terraform/gcp/variables.tf

@@ -68,5 +68,5 @@ variable "redis_mem" {
 }
 
 variable "image" {
-  default = "fleet:v4.27.0"
+  default = "fleet:v4.27.1"
 }

infrastructure/loadtesting/terraform/readme.md

@@ -43,9 +43,9 @@ There are a few main places of interest to monitor the load and resource usage:
 
 #### Using a release tag instead of a branch
 
-Since the tag name on Dockerhub doesn't match the tag name on GitHub, this presents a special use case when wanting to deploy a release tag.  In this case, you can use the optional `-var github_branch` in order to specify the separate tag.  For example, you would use the following to deploy a loadtest of version 4.27.0:
+Since the tag name on Dockerhub doesn't match the tag name on GitHub, this presents a special use case when wanting to deploy a release tag.  In this case, you can use the optional `-var github_branch` in order to specify the separate tag.  For example, you would use the following to deploy a loadtest of version 4.27.1:
 
-`terraform apply -var tag=v4.27.0 -var github_branch=fleet-v4.27.0 -var loadtest_containers=8`
+`terraform apply -var tag=v4.27.1 -var github_branch=fleet-v4.27.1 -var loadtest_containers=8`
 
 #### General Troubleshooting
 

infrastructure/sandbox/PreProvisioner/lambda/deploy_terraform/main.tf

@@ -157,7 +157,7 @@ resource "helm_release" "main" {
 
   set {
     name  = "imageTag"
-    value = "v4.27.0"
+    value = "v4.27.1"
   }
 
   set {

tools/fleetctl-npm/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fleetctl",
-  "version": "v4.27.0",
+  "version": "v4.27.1",
   "description": "Installer for the fleetctl CLI tool",
   "bin": {
     "fleetctl": "./run.js"