Skip to content

Commit

Permalink
Merge pull request #38 from vshn/update-docs-with-k8s-tokens
Browse files Browse the repository at this point in the history
Update installation guide
  • Loading branch information
zugao authored Jan 9, 2023
2 parents 8bcf772 + 08f9f0f commit 46c5cd5
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion docs/modules/ROOT/pages/how-tos/installation.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,17 +8,23 @@ It also requires an Exoscale IAMKey and a Kubernetes/OpenShift Service Account t

== Sources

The data is matched from k8s cluster and Exoscale organization.
The data is matched from a k8s cluster and an Exoscale organization.
The Kubernetes Service Account token is required to have `get` permissions on `Namespaces` and to the following managed resources:

* `buckets.exoscale.crossplane.io`
* `postgresqls.exoscale.crossplane.io`
* `mysqls.exoscale.crossplane.io`
* `redis.exoscale.crossplane.io`
* `kafkas.exoscale.crossplane.io`
* `opensearches.exoscale.crossplane.io`

=== Exoscale organization
The Access Key (IAM Key) from an Exoscale organization is required to have read access across all managed resources (e.g. SOS buckets, Postgres, etc).

=== K8s cluster
The access to the desired cluster from where the metrics should be collected has to be configured. The current configuration for each instance is done in the
`syn-tenant-repo` under `manifests/<desired-cluster>/billing`

== Example

[source,yaml]
Expand Down

0 comments on commit 46c5cd5

Please sign in to comment.