You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-votes-redis/README.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,12 +43,19 @@ The YAML documents in [azure-vote-managed-redis.yaml](azure-vote-managed-redis.y
43
43
44
44
The redis.cache.azure.com instance is configured to retrieve two secrets that are produced by the Azure Cache for Redis instance - hostname and primaryKey. As described [here](https://azure.github.io/azure-service-operator/guide/secrets/#how-to-retrieve-secrets-created-by-azure), these secrets need to be mapped to our sample application and the container for our sample application will be blocked until these two secrets are created.
45
45
46
-
The Voting Sample is configured with environment variables that read the secretes for the managed Redis hostname and access key, allowing the sample to use the cache.
46
+
The Voting Sample is configured with environment variables that read the secrets for the managed Redis hostname and access key, allowing the sample to use the managed cache.
47
+
48
+
### Steps to install
49
+
1. Create environment variables to hold app name. This APP_NAME below is used to generate the names of some resources in Azure below.
50
+
```sh
51
+
export APP_NAME=my-azure-vote
52
+
```
53
+
**Warning:**: Some of these names must be unique, so we recommend you edit APP_NAME above to be something unique to yourself to avoid conflicts. For example: APP_NAME=annas-voting-app
The operator will start creating the resource group and Azure Cache for Redis instance in Azure.
@@ -76,10 +83,9 @@ If you're interested in code for the application, it is available [here](https:/
76
83
77
84
## Clean up
78
85
79
-
When you're finished with the sample application you can clean all of the Kubernetes and Azure resources up by deleting the `cosmos-todo` namespace in your cluster.
86
+
When you're finished with the sample application you can clean all of the Kubernetes and Azure resources up by deleting the `azure-vote` namespace in your cluster.
80
87
```sh
81
-
kubectl delete namespace cosmos-todo
88
+
kubectl delete namespace azure-vote
82
89
```
83
90
84
-
Kubernetes will delete the web application pod and the operator will delete the Azure resource group and all the Cosmos DB resources.
85
-
(Deleting a Cosmos DB account can take several minutes.)
91
+
Kubernetes will delete the web application pod and the operator will delete the Azure resource group and resources.
0 commit comments