Skip to content

Commit

Permalink
Merge pull request #100 from practo/v1.1.0
Browse files Browse the repository at this point in the history
v1.1.0 release
  • Loading branch information
alok87 authored Jul 21, 2020
2 parents edff883 + 113ba6d commit b05d967
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 4 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -222,12 +222,12 @@ git pull origin master
- Build and push the image to `hub.docker.com/practodev`. Note: practodev push access is required.
```
git fetch --tags
git tag v1.0.0
git tag v1.1.0
make push
```
Note: For every tag major and major minor versions tags also available. For example: `v1` and `v1.0`
Note: For every tag major and major minor versions tags also available. For example: `v1` and `v1.1`
- Create a Release in Github. Refer [this](https://github.com/practo/k8s-worker-pod-autoscaler/releases/tag/v1.0.0) and create a release. Release should contain the Changelog information of all the issues and pull request after the last release.
- Create a Release in Github. Refer [this](https://github.com/practo/k8s-worker-pod-autoscaler/releases/tag/v1.1.0) and create a release. Release should contain the Changelog information of all the issues and pull request after the last release.
- Publish the release in Github 🎉
Expand Down
18 changes: 17 additions & 1 deletion UPGRADE.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,22 @@
# Upgrade Worker Pod Autoscaler

## Upgrade from v0.2 to v1
## Upgrade from v1.0 to v1.1

### Breaking Changes
There is no backward breaking change from `v1.0` to `v1.1`.

### Recommended Actions
Update the WorkerPodAutoScaler CRD to give WPA access to fetch Replicaset.
```
kubectl apply -f ./artifacts/crd.yaml
```

Note: Support for `v1alpha1` will be discontinued from `v1.2`.

### Changes
- [v1.1.0](https://github.com/practo/k8s-worker-pod-autoscaler/releases/tag/v1.1.0)

## Upgrade from v0.2 to v1.0

### Breaking Changes
There is no backward breaking change from `v0.2` to `v1`.
Expand Down

0 comments on commit b05d967

Please sign in to comment.