Skip to content

PC-904 dzKarp health monitor#315

Merged
mutantkeyboard merged 3 commits into
mainfrom
dzkarp_healthcheck
Mar 12, 2026
Merged

PC-904 dzKarp health monitor#315
mutantkeyboard merged 3 commits into
mainfrom
dzkarp_healthcheck

Conversation

@mutantkeyboard
Copy link
Copy Markdown
Contributor

@mutantkeyboard mutantkeyboard commented Mar 9, 2026

[HealthManager for dzKarp]

📚 Description of Changes

Provide an overview of your changes and why they’re needed. Link to any related issues (e.g., "Fixes #123"). If your PR fixes a bug, resolves a feature request, or updates documentation, please explain how.

  • What Changed:
    (Describe the modifications, additions, or removals.)

  • Why This Change:
    (Explain the problem this PR addresses or the improvement it provides.)

  • Affected Components:
    (Which component does this change affect? - put x for all components)

  • Compose

  • K8s

  • Other (please specify)

❓ Motivation and Context

Why is this change required? What problem does it solve?

🔍 Types of Changes

Indicate which type of changes your code introduces (check all that apply):

  • BUGFIX: Non-breaking fix for an issue.
  • NEW FEATURE: Non-breaking addition of functionality.
  • BREAKING CHANGE: Fix or feature that causes existing functionality to not work as expected.
  • ENHANCEMENT: Improvement to existing functionality.
  • CHORE: Changes that do not affect production (e.g., documentation, build tooling, CI).

🔬 QA / Verification Steps

Describe the steps a reviewer should take to verify your changes:

  1. (Step one: e.g., "Run make test to verify all tests pass.")
  2. (Step two: e.g., "Deploy to a Kind cluster with make create-kind && make deploy.")
  3. (Additional steps as needed.)

✅ Global Checklist

Please check all boxes that apply:

  • I have read and followed the CONTRIBUTING guidelines.
  • My code follows the code style of this project.
  • I have updated the documentation as needed.
  • I have added tests that cover my changes.
  • All new and existing tests have passed locally.
  • I have run this code in a local environment to verify functionality.
  • I have considered the security implications of this change.

@gitar-bot
Copy link
Copy Markdown

gitar-bot Bot commented Mar 9, 2026

Important

Upgrade your plan to unlock code review, CI analysis, custom rules, and more.

Comment thread internal/health/node_operator_monitor.go Outdated
Comment thread internal/health/node_operator_monitor.go Outdated
Comment thread internal/health/node_operator_monitor.go Outdated
Copy link
Copy Markdown
Contributor

@kevin-devzero kevin-devzero left a comment

Choose a reason for hiding this comment

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

looks better! lets try in preprod

// isDevZeroImage checks whether the deployment uses a DevZero container image.
func isDevZeroImage(dep *appsv1.Deployment) bool {
for _, c := range dep.Spec.Template.Spec.Containers {
if strings.HasPrefix(c.Image, devzeroImagePrefix) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

maybe substring instead of prefix

@mutantkeyboard mutantkeyboard merged commit 6e8b635 into main Mar 12, 2026
26 of 29 checks passed
@mutantkeyboard mutantkeyboard deleted the dzkarp_healthcheck branch March 12, 2026 13:01
Parthiba-Hazra pushed a commit that referenced this pull request May 5, 2026
* dzKarp health monitor

* Better allocations and error checking for response body

* Implement requested changes
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.

2 participants