Merge pull request #749 from mgsharm/release/v1.6.0

Prepare for Release/v1.6.0

Author: mgsharm

CHANGELOG.md

@@ -1,3 +1,22 @@
+# 1.6.0
+## General
+
+Added
+* Allow customization of service annotations in Helm values ([#738] thanks @mbovo)
+* Allow arbitrary labels and annotations to be added to all or select workloads ([#742] thanks @grumps)
+
+Fixed
+* script: use --update=none for mv in publish-charts ([#731])
+
+Misc
+* Upgrade dependencies ([#732], [#744])
+
+[#731]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/731
+[#732]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/732
+[#738]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/738
+[#742]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/742
+[#744]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/744
+
 # 1.5.0
 ## General
 
@@ -274,7 +293,7 @@ Instead of having the independent controller and agent cooperate and pass messag
 The agent performs all cluster object mutation operations via the API Server.
 [Service Account Token Volume Projection](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection) is used in API Server instead of the usual Kubernetes [rbac](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) system for authorization to limit sufficient permissions for any node being able to modify any other nodes.
 
-Brupop 0.2.0 also integrates with [Prometheus](https://prometheus.io/docs/instrumenting/clientlibs/) by exposing an HTTP endpoint from which Prometheus can gather metrics, allowing customers insight into the actions that the operator is taking. 
+Brupop 0.2.0 also integrates with [Prometheus](https://prometheus.io/docs/instrumenting/clientlibs/) by exposing an HTTP endpoint from which Prometheus can gather metrics, allowing customers insight into the actions that the operator is taking.
 
 
 Fixed:
@@ -292,13 +311,13 @@ Removed:
 * Deprecated updog platform integration in favor of Bottlerocket API ([#60])
 
 [#74]: https://github.com/bottlerocket-os/bottlerocket-update-operator/issues/74
-[#71]: https://github.com/bottlerocket-os/bottlerocket-update-operator/issues/71 
-[#68]: https://github.com/bottlerocket-os/bottlerocket-update-operator/issues/68 
+[#71]: https://github.com/bottlerocket-os/bottlerocket-update-operator/issues/71
+[#68]: https://github.com/bottlerocket-os/bottlerocket-update-operator/issues/68
 [#60]: https://github.com/bottlerocket-os/bottlerocket-update-operator/issues/60
 [#132]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/132
 [#147]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/147
 [#101]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/101
-[#85]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/85 
+[#85]: https://github.com/bottlerocket-os/bottlerocket-update-operator/pull/85
 
 # 0.1.5
 

README.md

@@ -92,7 +92,7 @@ namespace: "brupop-bottlerocket-aws"
 
 # The image to use for brupop
 # This defaults to the image built alongside a particular helm chart, but you can override it by uncommenting this line:
-# image: "public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.5.0"
+# image: "public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.6.0"
 
 # Placement controls
 # See the Kubernetes documentation about placement controls for more details:
@@ -299,8 +299,8 @@ will concurrently update up to `MAX_CONCURRENT_UPDATE` nodes respecting [PodDisr
 When `MAX_CONCURRENT_UPDATE` is set to `unlimited`, bottlerocket update operator
 will concurrently update all nodes respecting [PodDisruptionBudgets](https://kubernetes.io/docs/tasks/run-application/configure-pdb/).
 
-Note: The `MAX_CONCURRENT_UPDATE` configuration does not work well with `EXCLUDE_FROM_LB_WAIT_TIME_IN_SEC` 
-configuration, especially when `MAX_CONCURRENT_UPDATE` is set to `unlimited`, it could potentially exclude all 
+Note: The `MAX_CONCURRENT_UPDATE` configuration does not work well with `EXCLUDE_FROM_LB_WAIT_TIME_IN_SEC`
+configuration, especially when `MAX_CONCURRENT_UPDATE` is set to `unlimited`, it could potentially exclude all
 nodes from load balancer at the same time.
 
 To enable this feature, set the `max_concurrent_updates` value in your helm values yaml file to a positive integer value or `unlimited`. For example,
@@ -370,7 +370,7 @@ If you still decide to use these settings, please use "hour:00:00" format only i
 To enable this feature, set the `update_window_start` and `update_window_stop` values in your helm values yaml file to a `hour:minute:second` formatted value (UTCE 24-hour time notation).
 For example: `update_window_start: "08:0:0"` and `update_window_stop: "12:30:0"`.
 
-Otherwise, go to `bottlerocket-update-operator.yaml` and change `UPDATE_WINDOW_START` and `UPDATE_WINDOW_STOP` to a `hour:minute:second` formatted value (UTC (24-hour time notation)). 
+Otherwise, go to `bottlerocket-update-operator.yaml` and change `UPDATE_WINDOW_START` and `UPDATE_WINDOW_STOP` to a `hour:minute:second` formatted value (UTC (24-hour time notation)).
 
 Note that `UPDATE_WINDOW_START` is inclusive and `UPDATE_WINDOW_STOP` is exclusive.
 
@@ -415,8 +415,8 @@ kubectl get nodes
 ```
 Make a note of all the node names that you would like the Bottlerocket update operator to manage.
 
-Next, add the `updater-interface-version` label to the nodes. 
-For each node, use this command to add `updater-interface-version` label. 
+Next, add the `updater-interface-version` label to the nodes.
+For each node, use this command to add `updater-interface-version` label.
 Make sure to change `NODE_NAME` with the name collected from the previous command:
 
 ```sh
@@ -494,21 +494,21 @@ This view will inform you of the current Bottlerocket version of each node manag
 The following command requires `kubectl` to be configured for the desired cluster to be monitored:
 
 ``` sh
-kubectl get bottlerocketshadows --namespace brupop-bottlerocket-aws 
+kubectl get bottlerocketshadows --namespace brupop-bottlerocket-aws
 ```
 
 You can shorten this with:
 
 ``` sh
-kubectl get brs --namespace brupop-bottlerocket-aws 
+kubectl get brs --namespace brupop-bottlerocket-aws
 ```
 
 You should see output akin to the following:
 
 ```
-$ kubectl get brs --namespace brupop-bottlerocket-aws 
+$ kubectl get brs --namespace brupop-bottlerocket-aws
 NAME                                               STATE   VERSION   TARGET STATE   TARGET VERSION
-brs-node-1                                         Idle    1.5.2     Idle           
+brs-node-1                                         Idle    1.5.2     Idle
 brs-node-2                                         Idle    1.5.1     StagedUpdate   1.5.2
 ```
 
@@ -529,19 +529,19 @@ Now that Prometheus is running in the cluster, you can use the UI provided to vi
 Get the Prometheus pod name (e.g. `prometheus-deployment-5554fd6fb5-8rm25`):
 
 ```sh
-kubectl get pods --namespace brupop-bottlerocket-aws 
+kubectl get pods --namespace brupop-bottlerocket-aws
 ```
 
 Set up port forwarding to access Prometheus on the cluster:
 
 ```sh
-kubectl port-forward $prometheus-pod-name 9090:9090 --namespace brupop-bottlerocket-aws 
+kubectl port-forward $prometheus-pod-name 9090:9090 --namespace brupop-bottlerocket-aws
 ```
 
 Point your browser to `localhost:9090/graph` to access the sample Prometheus UI.
 
 Search for:
-* `brupop_hosts_state` to check how many hosts are in each state. 
+* `brupop_hosts_state` to check how many hosts are in each state.
 * `brupop_hosts_version` to check how many hosts are in each Bottlerocket version.
 
 
@@ -596,13 +596,13 @@ Because mutations to a node are orchestrated through the API server component, s
 To get logs for the API server, run the following:
 
 ```sh
-kubectl logs deployment/brupop-apiserver --namespace brupop-bottlerocket-aws 
+kubectl logs deployment/brupop-apiserver --namespace brupop-bottlerocket-aws
 ```
 
 The controller logs will usually not help troubleshoot issues about the state of updates in a cluster, but they can similarly be fetched:
 
 ```sh
-kubectl logs deployment/brupop-controller-deployment --namespace brupop-bottlerocket-aws 
+kubectl logs deployment/brupop-controller-deployment --namespace brupop-bottlerocket-aws
 ```
 
 ### Why are updates stuck in my cluster?
@@ -625,7 +625,7 @@ kubectl get pods --selector=brupop.bottlerocket.aws/component=agent -o wide --na
 Then fetch the logs for that agent:
 
 ```sh
-kubectl logs brupop-agent-podname --namespace brupop-bottlerocket-aws 
+kubectl logs brupop-agent-podname --namespace brupop-bottlerocket-aws
 ```
 
 ### Why are my bottlerocket nodes egressing to `https://updates.bottlerocket.aws`?

VERSION

@@ -1 +1 @@
-v1.5.0
+v1.6.0

bottlerocket-update-operator.yaml

@@ -540,7 +540,7 @@ spec:
               value: "true"
             - name: TRACING_FILTER_DIRECTIVE
               value: "info"
-          image: public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.5.0
+          image: public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.6.0
           name: brupop
           resources:
             limits:
@@ -647,7 +647,7 @@ spec:
               value: "true"
             - name: TRACING_FILTER_DIRECTIVE
               value: "info"
-          image: public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.5.0
+          image: public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.6.0
           livenessProbe:
             httpGet:
               path: /ping
@@ -738,7 +738,7 @@ spec:
               value: "true"
             - name: TRACING_FILTER_DIRECTIVE
               value: "info"
-          image: public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.5.0
+          image: public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.6.0
           name: brupop
           resources:
             limits:
@@ -747,7 +747,7 @@ spec:
               cpu: 10m
               memory: 40Mi
       priorityClassName: "brupop-controller-high-priority"
-      
+
       serviceAccountName: brupop-controller-service-account
 ---
 # Source: bottlerocket-update-operator/templates/cert-manager-agent-cert.yaml

deploy/charts/bottlerocket-update-operator/Chart.yaml

@@ -4,7 +4,7 @@ description: A Helm chart for the Bottlerocket Update Operator
 home: https://github.com/bottlerocket-os/bottlerocket-update-operator
 icon: https://avatars.githubusercontent.com/u/61023959?s=200&v=4
 type: application
-version: 1.5.0
-appVersion: "1.5.0"
+version: 1.6.0
+appVersion: "1.6.0"
 sources:
   - https://github.com/bottlerocket-os/bottlerocket-update-operator

deploy/charts/bottlerocket-update-operator/README.md

@@ -78,7 +78,7 @@ The following configuration values are supported:
 namespace: "brupop-bottlerocket-aws"
 
 # The image to use for brupop
-image: "public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.5.0"
+image: "public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.6.0"
 
 # Provide pod level labels and annotations for all brupop workloads
 podLabels: {}

deploy/charts/bottlerocket-update-operator/values.yaml

@@ -4,7 +4,7 @@
 namespace: "brupop-bottlerocket-aws"
 
 # The image to use for brupop
-image: "public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.5.0"
+image: "public.ecr.aws/bottlerocket/bottlerocket-update-operator:v1.6.0"
 
 # Placement controls
 # See the Kubernetes documentation about placement controls for more details:
@@ -56,7 +56,7 @@ placement:
 
 # External load balancer setting.
 # When `exclude_from_lb_wait_time_in_sec` is set to positive value
-# brupop will exclude the node from load balancer and 
+# brupop will exclude the node from load balancer and
 # wait for `exclude_from_lb_wait_time_in_sec` seconds before draining node.
 exclude_from_lb_wait_time_in_sec: "0"