Skip to content

Remove KProbe logic from Drainer #2324

Open

Description

@nader-ziada

/area networking

Follow up from Serving PR: knative/serving#12033

A related concern (but I don't think it should block this PR) is why the drainer has KProbe logic in it
https://github.com/knative/pkg/blob/main/network/handlers/drain.go#L157

I think that makes the network.NewProbeHandler a noop in this instance
https://github.com/knative/networking/blob/main/pkg/probe_handler.go#L37

Activity

  1. dprotaso commented on Oct 26, 2021

    @dprotaso
    Member

    cc @runzexia who included the KProbe logic in the drainer - is there a reason you couldn't consume the handler from knative.dev/networking ?

  2. github-actions commented on Jan 25, 2022

    @github-actions
    Contributor

    This issue is stale because it has been open for 90 days with no
    activity. It will automatically close after 30 more days of
    inactivity. Reopen the issue with /reopen. Mark the issue as
    fresh by adding the comment /remove-lifecycle stale.

  3. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jan 25, 2022
  4. pierDipi commented on Jan 25, 2022

    @pierDipi
    Contributor

    /remove-lifecycle stale

  5. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jan 25, 2022
  6. github-actions commented on Apr 26, 2022

    @github-actions
    Contributor

    This issue is stale because it has been open for 90 days with no
    activity. It will automatically close after 30 more days of
    inactivity. Reopen the issue with /reopen. Mark the issue as
    fresh by adding the comment /remove-lifecycle stale.

  7. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 26, 2022
  8. dprotaso commented on Apr 26, 2022

    @dprotaso
    Member

    /lifecycle frozen

  9. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/networkinglifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions