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(controller): revert instrumentation when Dash0 resource is deleted #9

Merged

Conversation

basti1302
Copy link
Member

No description provided.

@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch 5 times, most recently from 240a7de to 14cd907 Compare May 28, 2024 16:05
@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch from 14cd907 to 7d59f26 Compare May 28, 2024 16:07
@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch 2 times, most recently from 7dcb8b2 to 3235ebb Compare May 28, 2024 16:33
* add read permissions for namespaces
* remove all permissions (get, list, watch) for pods

Also: Order the kubebuilder:rbac statements in dash0_controller
alphabetically.
@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch from 3235ebb to e135648 Compare May 28, 2024 16:34
This helps to consolidate the instrument/revert logic into one method,
instead of having one method per resource type.
@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch from 72f08ca to ad1e5cd Compare May 29, 2024 08:21
This happens both when a workload is already instrumented, but also for
replica sets that are owned by a deployment, so we should mention this
in the corresponding log message and event.
@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch from ab88e01 to ef50d2b Compare May 30, 2024 13:01
@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch from f828e0e to 449903f Compare May 31, 2024 15:46
@basti1302 basti1302 marked this pull request as ready for review May 31, 2024 18:51
Also: prefix all labels with dash0.com and use kebap case instead of
dot-separated notation for label names.
@basti1302 basti1302 force-pushed the remove-instrumentation-when-dash0-custom-resource-is-deleted branch from 7f3b7f6 to 612d403 Compare May 31, 2024 18:55
Copy link

sonarcloud bot commented May 31, 2024

Quality Gate Passed Quality Gate passed

Issues
1 New issue
1 Accepted issue

Measures
0 Security Hotspots
No data about Coverage
2.3% Duplication on New Code

See analysis details on SonarCloud

@basti1302 basti1302 enabled auto-merge (rebase) May 31, 2024 18:56
@basti1302 basti1302 merged commit 040820e into main May 31, 2024
4 checks passed
@basti1302 basti1302 deleted the remove-instrumentation-when-dash0-custom-resource-is-deleted branch May 31, 2024 19:00
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.

1 participant