Skip to content

Commit 68c4186

Browse files
committed
fix readme
1 parent bedd26c commit 68c4186

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

README.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,20 +11,18 @@ the [post that presents Iris](https://blog.doit-intl.com/iris-3-automatic-labeli
1111

1212
Iris automatically assigns labels to Google Cloud Platform resources for easier analysis, particularly of cost.
1313

14-
Resources of all supported types in all or some of the projects in the GCP organization will get automatically-generated labels with keys like `iris_zone` (the prefix is configurable), and a value copied from the resource. For example, a Google
15-
Compute Engine instance would get labels like
16-
`[iris_name:nginx]`, `[iris_region:us-central1]` and `[iris_zone:us-central1-a]`. This behavior can be configured in
17-
various ways; see below.
14+
Resources of all supported types in all or some of the projects in the GCP organization will get automatically-generated labels with keys like `iris_zone` (the prefix is configurable), and a value copied from the resource. For example, a Google Compute Engine instance would get labels like
15+
`[iris_name:nginx]`, `[iris_region:us-central1]` and `[iris_zone:us-central1-a]`. This behavior can be configured in various ways; see below.
1816

1917
## Note: Organization focus
2018

21-
Note that Iris is designed to serve the organization. It is not designed around serving a single project (though you can configure that).
19+
Note that Iris is designed to serve the organization. It is not designed around serving a single project (though you can configure that). Only one instance of Iris runs at any one time in an organization.
2220

2321
## Iris doesn't add new information
2422

2523
Iris does not *add* information, only *copy* values that already exist. For example, it can label a VM instance with its zone; but it cannot add a "business unit" label because it does not know a resource's business unit. For that, you should label all resources when creating them, e.g., in your Terraform scripts. (Indeed, iris can be made extraneous in this way.)
2624

27-
## Labeling resources that existing resources when you deploy Iris
25+
## Labeling existing resources when you deploy Iris
2826

2927
If you want to label lots of virtual machines,PubSub topics etc. that *already exist* when you deploy Iris, see section "[Labeling existing resources](#labeling-existing-resources)" below.
3028

0 commit comments

Comments
 (0)