Update getting_started.md with new version; update releasing steps (#641)

This commit is contained in:
Alexander Matyushentsev 2018-09-24 15:43:06 -07:00 committed by GitHub
parent 3577a68d2d
commit 523c7ddf82
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 14 additions and 12 deletions

View file

@ -1,26 +1,25 @@
# Changelog
## v0.9.0
## v0.9.1 (2018-09-24)
- Repo server unable to execute ls-remote for private repos (issue #639)
## v0.9.0 (2018-09-24)
### Notes about upgrading from v0.8
* The `server.crt` and `server.key` fields of `argocd-secret` had been renamed to `tls.crt` and `tls.key` for
better integration with cert manager(issue #617). Existing `argocd-secret` should be updated accordingly to
preserve existing TLS certificate.
* Cluster wide resources should be allowed in default project (due to issue #330):
```
argocd project allow-cluster-resource default '*' '*'
```
### Breaking changes v0.8
* Projects now provide the ability to allow or deny deployments of cluster-scoped resources
(e.g. Namespaces, ClusterRoles, CustomResourceDefinitions). When upgrading from v0.8 to v0.9, to
match the behavior of v0.8 (which did not have restrictions on deploying resources) and continue to
allow deployment of cluster-scoped resources, an additional command should be run:
```bash
argocd proj allow-cluster-resource default '*'
argocd proj allow-cluster-resource default '*' '*'
```
The above command allows the `default` project to deploy any cluster-scoped resources which matches

View file

@ -9,7 +9,7 @@ An example guestbook application is provided to demonstrate how ArgoCD works.
## 1. Install ArgoCD
```bash
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v0.8.2/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v0.9.1/manifests/install.yaml
```
This will create a new namespace, `argocd`, where ArgoCD services and application resources will live.
@ -31,7 +31,7 @@ brew install argoproj/tap/argocd
On Linux:
```bash
curl -sSL -o /usr/local/bin/argocd https://github.com/argoproj/argo-cd/releases/download/v0.8.2/argocd-linux-amd64
curl -sSL -o /usr/local/bin/argocd https://github.com/argoproj/argo-cd/releases/download/v0.9.1/argocd-linux-amd64
chmod +x /usr/local/bin/argocd
```

View file

@ -3,8 +3,9 @@
1. Tag, build, and push argo-cd-ui
```bash
cd argo-cd-ui
git checkout -b release-X.Y
git tag vX.Y.Z
git push upstream vX.Y.Z
git push upstream release-X.Y --tags
IMAGE_NAMESPACE=argoproj IMAGE_TAG=vX.Y.Z DOCKER_PUSH=true yarn docker
```
@ -19,7 +20,7 @@ git push upstream release-X.Y
vi manifests/base/kustomization.yaml # update with new image tags
make manifests
git commit -a -m "Update manifests to vX.Y.Z"
git push upstream master
git push upstream release-X.Y
```
4. Tag, build, and push release to docker hub

View file

@ -25,7 +25,9 @@ resources:
imageTags:
- name: argoproj/argocd-server
newTag: latest
- name: argoproj/argocd-ui
newTag: latest
- name: argoproj/argocd-repo-server
newTag: latest
- name: argoproj/application-controller
- name: argoproj/argocd-application-controller
newTag: latest