Skip to content

Commit

Permalink
Update docs for v2.7.0 release (#3972)
Browse files Browse the repository at this point in the history
  • Loading branch information
@matthchr
matthchr committed Apr 29, 2024
1 parent cb834b3 commit 8a43960
Show file tree
Hide file tree
Showing 8 changed files with 43 additions and 92 deletions.
18 changes: 9 additions & 9 deletions ROADMAP.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,11 @@ We target a new release of ASO approximately every two months, though this may v

Our current release plan:

| Version | Estimated Release |
| ------- | -----------------:|
| [2.7.0](https://github.com/Azure/azure-service-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2.7.0) | Mid April 2024 |
| [2.8.0](https://github.com/Azure/azure-service-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2.8.0) | Mid June 2024 |
| [2.9.0](https://github.com/Azure/azure-service-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2.9.0) | Mid August 2024 |
| 2.10.0 | Mid October 2024 |
| Version | Estimated Release |
|-----------------------------------------------------------------------------------------------------------|------------------:|
| [2.8.0](https://github.com/Azure/azure-service-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2.8.0) | Mid June 2024 |
| [2.9.0](https://github.com/Azure/azure-service-operator/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2.9.0) | Mid August 2024 |
| [2.10.0](https://github.com/Azure/azure-service-operator/milestone/29) | Mid October 2024 |

Where linked, versions go to a list of feature and bugs that are planned to be included in that release.

Expand All @@ -31,9 +30,10 @@ We publish an [experimental release](https://github.com/Azure/azure-service-oper

Prior GA releases of ASO v2:

| Version | Release Date | |
| ---------------------------------------------------------------------------- | ----------------:| --- |
| [2.6.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.6.0) | 23 February 2023 | |
| Version | Release Date | |
|------------------------------------------------------------------------------|-----------------:|-----|
| [2.7.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.7.0) | 25 April 2024 |
| [2.6.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.6.0) | 23 February 2024 | |
| [2.5.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.5.0) | 7 December 2023 | (1) |
| [2.4.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.4.0) | 14 November 2023 | |
| [2.3.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.3.0) | 5 September 2023 | |
Expand Down
31 changes: 12 additions & 19 deletions docs/hugo/content/contributing/create-a-new-release.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,16 +26,16 @@ service Swagger specifications. We must validate each breaking change so that we
1. Download the CRD definitions for the prior release (in this example, v2.5.0):

``` bash
wget https://github.com/Azure/azure-service-operator/releases/download/v2.5.0/azureserviceoperator_v2.5.0.yaml
wget https://github.com/Azure/azure-service-operator/releases/download/v2.6.0/azureserviceoperator_customresourcedefinitions_v2.6.0.yaml
```

2. Download the CRD definitions for the new release (in this example, v2.6.0):

``` bash
wget https://github.com/Azure/azure-service-operator/releases/download/v2.6.0/azureserviceoperator_v2.6.0.yaml
wget https://github.com/Azure/azure-service-operator/releases/download/v2.7.0/azureserviceoperator_customresourcedefinitions_v2.7.0.yaml
```

This will only be available when the GitHub action trigged by publishing the release has finished.
This will only be available when the GitHub action triggered by publishing the release has finished.

3. Produce a diff between these files and examine it.

Expand Down Expand Up @@ -74,39 +74,32 @@ Perform a simple smoke test to make sure the new release is capable of starting
task controller:make-sp-secret
```

6. Download the operator from MCR.
6. Download asoctl

``` bash
wget https://github.com/Azure/azure-service-operator/releases/download/v2.3.0/azureserviceoperator_v2.3.0.yaml

7. Configure [`crd-patterns`](https://azure.github.io/azure-service-operator/guide/crd-management/) to use with new release.

``` bash
sed -i 's_--crd-pattern=.*_--crd-pattern=resources.azure.com/*;network.azure.com/*_g' azureserviceoperator_v2.3.0.yaml
curl -L https://github.com/Azure/azure-service-operator/releases/latest/download/asoctl-linux-amd64.gz -o asoctl.gz
gunzip asoctl.gz
chmod +x asoctl
```

We use `sed` to replace the blank setting included in the release with the one we want to use, including both resource group and network CRDs.
7. Use asoctl to install the new release

8. Install the operator into your cluster

``` bash
kubectl apply --server-side=true -f azureserviceoperator_v2.0.0-beta.3.yaml
./asoctl export template --version v2.7.0 --crd-pattern "resources.azure.com/*;network.azure.com/*" | kubectl apply -f -
```

(We need to use [server-side apply](https://kubernetes.io/docs/reference/using-api/server-side-apply/) because the CRD for VirtualMachines is large enough that it can't fit in the `last-applied-configuration` annotation client-side `kubectl apply` uses.)

7. Watch while ASO starts
8. Watch while ASO starts
``` bash
kubectl get all -n azureserviceoperator-system
```

8. Create a resource group and a vnet in it (the vnet is to check that conversion webhooks are working, since there aren't any for RGs):
9. Create a resource group and a vnet in it (the vnet is to check that conversion webhooks are working, since there aren't any for RGs):

``` bash
kubectl apply -f v2/samples/resources/v1api/v1api20200601_resourcegroup.yaml
kubectl apply -f v2/samples/network/v1api20201101/v1api20201101_virtualnetwork.yaml
```
8. Make sure they deploy successfully - check in the portal as well.
10. Make sure they deploy successfully - check in the portal as well.

## Create and test the Helm chart

Expand Down

0 comments on commit 8a43960

Please sign in to comment.