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: Add support for configuring observability via WasmCloudHostConfig #53

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

joonas
Copy link
Member

@joonas joonas commented Jun 30, 2024

Feature or Problem

This adds the ability to configure the various observability options via WasmCloudHostConfig by adding:

apiVersion: k8s.wasmcloud.dev/v1alpha1
kind: WasmCloudHostConfig
metadata:
  name: my-wasmcloud-cluster
spec:
  ...
  observability:
    enable: true
    endpoint: "https://to.my.cluster.local.or.external.collector:4318"

It also has the ability to optionally override the endpoint for any of the signals, and the protocol (default is http)

Related Issues

Fixes #49

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
@joonas joonas force-pushed the feat/enable-observability branch from 8110957 to f83dbf9 Compare June 30, 2024 21:22
@@ -1,6 +1,6 @@
[package]
name = "wasmcloud-operator-types"
version = "0.1.5"
version = "0.1.6"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super Nit: Technically this should be 0.2.0 since you're adding new features

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you're absolutely right, this should probably be a 0.2.0, I think we've broken the rule about patch versions a number of times already, so I think we'll probably want to have that conversation when we do the work to move to v1alpha2.

#[serde(rename_all = "camelCase")]
pub struct ObservabilityConfiguration {
#[serde(default)]
pub enable: bool,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be adding the documentation to each of these options so people know what they do? I know we have the command line flags, but wasn't sure if we were documenting these or not

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should, I'll follow-up with a PR that does the documenting part, including the README

@joonas joonas merged commit bf8a74a into wasmCloud:main Jul 2, 2024
5 checks passed
@joonas joonas deleted the feat/enable-observability branch July 2, 2024 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ensure wasmcloud-operator can enable observability for the hosts it's deploying
2 participants