Not implemented - In analysis | -
Not implemented - Planned (#9) | -
Not implemented - In analysis | -
--deep-metrics-enabled
command-line flag. In this case, regardless of the value of the field `spec.(identity|metadata|authorization|response).metrics` in the AuthConfigs, individual metrics for all evaluators of all AuthConfigs will be exported.
+| Evaluator type | Metric's `evaluator_type` label |
+|-----------------------------------------------|---------------------------------|
+| `authentication.apiKey` | IDENTITY_APIKEY |
+| `authentication.kubernetesTokenReview` | IDENTITY_KUBERNETES |
+| `authentication.jwt` | IDENTITY_OIDC |
+| `authentication.oauth2Introspection` | IDENTITY_OAUTH2 |
+| `authentication.x509` | IDENTITY_MTLS |
+| `authentication.plain` | IDENTITY_PLAIN |
+| `authentication.anonymous` | IDENTITY_NOOP |
+| `metadata.http` | METADATA_GENERIC_HTTP |
+| `metadata.userInfo` | METADATA_USERINFO |
+| `metadata.uma` | METADATA_UMA |
+| `authorization.patternMatching` | AUTHORIZATION_JSON |
+| `authorization.opa` | AUTHORIZATION_OPA |
+| `authorization.kubernetesSubjectAccessReview` | AUTHORIZATION_KUBERNETES |
+| `authorization.spicedb` | AUTHORIZATION_AUTHZED |
+| `response.success..plain` | RESPONSE_PLAIN |
+| `response.success..json` | RESPONSE_JSON |
+| `response.success..wristband` | RESPONSE_WRISTBAND |
+
+Metrics at the level of the evaluators can also be enforced to an entire Authorino instance, by setting the --deep-metrics-enabled
command-line flag. In this case, regardless of the value of the field `spec.(authentication|metadata|authorization|response).metrics` in the AuthConfigs, individual metrics for all evaluators of all AuthConfigs will be exported.
For more information about metrics exported by Authorino, see [Observability](./user-guides/observability.md#metrics).
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 2acffc18..34dbb85b 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -51,11 +51,13 @@ Check out the [Feature specification](./features.md) page for more feature-speci
The simplest way to install the Authorino Operator is by applying the manifest bundle:
```sh
-kubectl apply -f https://raw.githubusercontent.com/Kuadrant/authorino-operator/main/config/deploy/manifests.yaml
+curl -sL https://raw.githubusercontent.com/Kuadrant/authorino-operator/main/utils/install.sh | bash -s
```
The above will install the latest build of the Authorino Operator and latest version of the manifests (CRDs and RBAC), which by default points as well to the latest build of Authorino, both based on the `main` branches of each component. To install a stable released version of the Operator and therefore also defaults to its latest compatible stable release of Authorino, replace `main` with another tag of a proper release of the Operator, e.g. 'v0.2.0'.
+This step will also install [cert-manager](https://github.com/jetstack/cert-manager) in the cluster (required).
+
Alternatively, you can deploy the Authorino Operator using the Operator Lifecycle Manager bundles. For instructions, check out [Installing via OLM](https://github.com/kuadrant/authorino-operator#installing-via-olm).
### Step: Request an Authorino instance
@@ -72,12 +74,7 @@ The instructions here are for centralized gateway or centralized authorization s
kubectl create namespace authorino
```
- Deploy [cert-manager](https://github.com/jetstack/cert-manager) (skip if you already have certificates and certificate keys created and stored in Kubernetes `Secret`s in the namespace or cert-manager is installed and running in the cluster):
- ```sh
- kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.4.0/cert-manager.yaml
- ```
-
- Create the TLS certificates (skip if you already have certificates and certificate keys created and stored in Kubernetes `Secret`s in the namespace):
+ Create the TLS certificates (requires [cert-manager](https://github.com/jetstack/cert-manager); skip if you already have certificates and certificate keys created and stored in Kubernetes `Secret`s in the namespace):
```sh
curl -sSL https://raw.githubusercontent.com/Kuadrant/authorino/main/deploy/certs.yaml | sed "s/\$(AUTHORINO_INSTANCE)/authorino/g;s/\$(NAMESPACE)/authorino/g" | kubectl -n authorino apply -f -
```
@@ -138,12 +135,7 @@ The instructions here are for centralized gateway or centralized authorization s
kubectl create namespace myapp
```
- Deploy [cert-manager](https://github.com/jetstack/cert-manager) (skip if you already have certificates and certificate keys created and stored in Kubernetes `Secret`s in the namespace or cert-manager is installed and running in the cluster):
- ```sh
- kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.4.0/cert-manager.yaml
- ```
-
- Create the TLS certificates (skip if you already have certificates and certificate keys created and stored in Kubernetes `Secret`s in the namespace):
+ Create the TLS certificates (requires [cert-manager](https://github.com/jetstack/cert-manager); skip if you already have certificates and certificate keys created and stored in Kubernetes `Secret`s in the namespace):
```sh
curl -sSL https://raw.githubusercontent.com/Kuadrant/authorino/main/deploy/certs.yaml | sed "s/\$(AUTHORINO_INSTANCE)/authorino/g;s/\$(NAMESPACE)/myapp/g" | kubectl -n myapp apply -f -
```
@@ -346,25 +338,25 @@ For authentication based on OpenID Connect (OIDC) JSON Web Tokens (JWT), plus on
```sh
kubectl -n myapp apply -f -<