From 6ccd003f6b74a4b796b914b631754986d43b1ac5 Mon Sep 17 00:00:00 2001 From: adrienjt Date: Tue, 7 Jul 2020 10:19:01 -0700 Subject: [PATCH] v0.10.0-rc.0 version bump and changelog Signed-off-by: adrienjt --- CHANGELOG.md | 4 ++++ README.md | 6 +++--- charts/multicluster-scheduler/Chart.yaml | 4 ++-- charts/multicluster-scheduler/README.md | 8 ++++---- 4 files changed, 13 insertions(+), 9 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index b879aa21..6f6e1122 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -20,6 +20,10 @@ --> +## v0.10.0-rc.0 + +This release fixes a couple of bugs, one [with GKE route-based clusters](https://github.com/admiraltyio/multicluster-scheduler/issues/44) (vs.VPC-native), the other [with DNS horizontal autoscaling](https://github.com/admiraltyio/multicluster-scheduler/issues/43). As a side benefit, virtual nodes capacities and allocatable resources aren't dummy high values anymore, but the sum of the corresponding values over the nodes of the target clusters that they represent. We slipped in a small UX change: when you run `kubectl get nodes`, the role column will now say "cluster" for virtual nodes, rather than "agent", to help understand concepts. Last but not least, we're upgrading internally from Kubernetes 1.17 to 1.18. + ## v0.9.3 ### Bugfixes diff --git a/README.md b/README.md index f8c29931..d2a831c2 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,7 @@ kubectl --context "$CLUSTER2" create namespace admiralty helm install multicluster-scheduler admiralty/multicluster-scheduler \ --kube-context "$CLUSTER2" \ --namespace admiralty \ - --version 0.9.3 \ + --version 0.10.0-rc.0 \ --set clusterName=c2 ``` @@ -103,7 +103,7 @@ kubectl --context "$CLUSTER1" create namespace admiralty helm install multicluster-scheduler admiralty/multicluster-scheduler \ --kube-context "$CLUSTER1" \ --namespace admiralty \ - --version 0.9.3 \ + --version 0.10.0-rc.0 \ --set clusterName=c1 \ --set targetSelf=true \ --set targets[0].name=c2 @@ -303,7 +303,7 @@ jq '.targets += [{name: "c2"}]' | \ helm upgrade multicluster-scheduler admiralty/multicluster-scheduler \ --kube-context "$CLUSTER1" \ --namespace admiralty \ - --version 0.9.3 \ + --version 0.10.0-rc.0 \ -f - ``` diff --git a/charts/multicluster-scheduler/Chart.yaml b/charts/multicluster-scheduler/Chart.yaml index 2605e66c..1bca9a0d 100644 --- a/charts/multicluster-scheduler/Chart.yaml +++ b/charts/multicluster-scheduler/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v2 name: multicluster-scheduler -version: 0.9.3 +version: 0.10.0-rc.0 #kubeVersion: A SemVer range of compatible Kubernetes versions (optional) description: A system of Kubernetes controllers that intelligently schedules workloads across clusters. type: application @@ -14,5 +14,5 @@ home: https://github.com/admiraltyio/multicluster-scheduler # email: The maintainer's email (optional for each maintainer) # url: A URL for the maintainer (optional for each maintainer) icon: https://admiralty.io/icons/icon-144x144.png -appVersion: 0.9.3 +appVersion: 0.10.0-rc.0 #deprecated: Whether this chart is deprecated (optional, boolean) diff --git a/charts/multicluster-scheduler/README.md b/charts/multicluster-scheduler/README.md index 1a313500..ebdb6453 100644 --- a/charts/multicluster-scheduler/README.md +++ b/charts/multicluster-scheduler/README.md @@ -46,7 +46,7 @@ Create a namespace for multicluster-scheduler and install the chart in it, using ```sh kubectl create namespace admiralty helm install multicluster-scheduler admiralty/multicluster-scheduler \ - --version 0.9.3 \ + --version 0.10.0-rc.0 \ -n admiralty \ -f values.yaml ``` @@ -109,7 +109,7 @@ Don't forget to label multicluster-scheduler's namespace (e.g., "admiralty") wit | targets[].context | string | `""` | if using a custom kubeconfig secret, with multiple contexts, override the kubeconfig's current context | | imagePullSecretName | string | `""` | | | controllerManager.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-agent"` | | -| controllerManager.image.tag | string | `"0.9.3"` | | +| controllerManager.image.tag | string | `"0.10.0-rc.0"` | | | controllerManager.image.pullPolicy | string | `"IfNotPresent"` | | | controllerManager.resources | object | `{}` | | | controllerManager.nodeSelector | object | `{}` | | @@ -117,7 +117,7 @@ Don't forget to label multicluster-scheduler's namespace (e.g., "admiralty") wit | controllerManager.affinity | object | `{}` | | | controllerManager.tolerations | array | `[]` | | | scheduler.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-scheduler"` | | -| scheduler.image.tag | string | `"0.9.3"` | | +| scheduler.image.tag | string | `"0.10.0-rc.0"` | | | scheduler.image.pullPolicy | string | `"IfNotPresent"` | | | scheduler.resources | object | `{}` | | | scheduler.nodeSelector | object | `{}` | | @@ -125,7 +125,7 @@ Don't forget to label multicluster-scheduler's namespace (e.g., "admiralty") wit | scheduler.affinity | object | `{}` | | | scheduler.tolerations | array | `[]` | | | postDeleteJob.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-remove-finalizers"` | | -| postDeleteJob.image.tag | string | `"0.9.3"` | | +| postDeleteJob.image.tag | string | `"0.10.0-rc.0"` | | | postDeleteJob.image.pullPolicy | string | `"IfNotPresent"` | | | postDeleteJob.resources | object | `{}` | | | postDeleteJob.nodeSelector | object | `{}` | |