Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(sm/console): tags and custom props #4661

Merged
merged 13 commits into from
Dec 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
118 changes: 113 additions & 5 deletions docs/self-managed/console-deployment/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,11 +47,13 @@ To enable usage collection, configure the parameters described in the next secti

To enable telemetry, the following parameters need to be configured. Camunda will provide you with the customer ID (Camunda Docker username) needed to send telemetry data to Camunda.

| Parameter | Description | Example value |
| ---------------- | ----------------------------------------------------------------------------------- | --------------- |
| `customerId` | Unique identifier of the customer. This is also a Camunda Docker registry user name | `customername` |
| `installationId` | Unique installation ID of the current customer installation | `my-deployment` |
| `telemetry` | Telemetry config for Console Self-Managed: `disabled`, `online` or `download` | `online` |
| Parameter | Description | Example value |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- |
| `customerId` | Unique identifier of the customer. This is also a Camunda Docker registry username. | `customername` |
| `installationId` | Unique installation ID of the current customer installation. | `my-deployment` |
| `telemetry` | Telemetry config for Console Self-Managed: `disabled`, `online`, or `download`. | `online` |
| `managed.releases.tags` | Assign cluster tags to indicate what type of cluster it is. Default tags are `dev`, `stage`, `test`, or `prod`, but users can assign any custom tag. | `- dev` (list of strings) |
| `managed.releases.custom-properties` | List of custom properties users can add to their cluster with custom descriptions and custom links on the cluster details page. | See custom properties section |

Console environment variables could be set in Helm. For more details, check [Console Helm values](https://artifacthub.io/packages/helm/camunda/camunda-platform#console-parameters).
For example:
Expand All @@ -67,6 +69,112 @@ console:
value: online
```

### Override configuration parameters

Configuration parameters formerly replaced the complete configuration. Even if you only changed the `customerId`, the complete configuration still had to be added.

This is no longer the case with the override parameters. A subset of parameters can be set so individual parameters can be adjusted. If a parameter must be changed for a specific cluster, the `name` and `namespace` fields must be set with the exact values so correlations can be made accordingly.

#### Example

Given the following configuration provided by Helm:

```yaml
camunda:
console:
customerId: customer-id
installationId: camunda-platform-id-dev-console-sm-main
telemetry: disabled
managed:
method: plain
releases:
- name: camunda-platform
namespace: camunda-platform-namespace
version: 9.1.2
components:
- name: Console
id: console
version: ...
url: https://...
readiness: https://...
metrics: https://...
- name: Keycloak
id: keycloak
version: ...
url: https://...
- name: Identity
id: identity
version: ...
url: https://...
readiness: https://...
metrics: https://...
- name: WebModeler WebApp
id: webModelerWebApp
version: ...
url: https://...
- name: Zeebe Gateway
id: zeebeGateway
version: ...
urls:
grpc: grpc://...
http: https://...
readiness: https://...
metrics: https://...
- name: Zeebe
id: zeebe
version: ...
```

The following example of an `overrideConfiguration` changes the `customerId` and adds `tags` and `custom-properties` for the cluster with name `camunda-platform` in namespace `camunda-platform-namespace`:

```yaml
console:
overrideConfiguration:
camunda:
console:
customerId: "new-customer-id"
managed:
releases:
- name: camunda-platform
namespace: camunda-platform-namespace
tags:
- production
custom-properties:
- description: "This is a custom description of the cluster."
links:
- name: "Camunda"
url: "https://camunda.com"
- name: "Camunda Docs"
url: "https://docs.camunda.io"
- name: "Grafana"
url: "https://..."
```

### Custom properties

Custom properties are useful to add custom information to the **Cluster details** page in Console. A custom property contains a description and multiple links.

The following example shows one custom property for a cluster:

```yaml
console:
overrideConfiguration:
camunda:
console:
customerId: "new-customer-id"
managed:
releases:
- name: camunda-platform
namespace: camunda-platform
custom-properties:
- description: "Useful links to Camunda resources."
links:
- name: "Camunda Blog"
url: "https://camunda.com/blog/"
- name: "Camunda Docs"
url: "https://docs.camunda.io"
```

## Using a different OpenID Connect (OIDC) authentication provider than Keycloak

By default, Console uses Keycloak to provide authentication.
Expand Down
Loading
Loading