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

Set anti-affinity for receiver deployment #483

Merged

Conversation

arghya88
Copy link
Contributor

@arghya88 arghya88 commented Dec 15, 2020

Signed-off-by: Arghya Sadhu arghya88@gmail.com

Fixes #482

Proposed Changes

  • Set anti-affinity for receiver deployment

Release Note

Receivers now specify anti-affinity so that replicas will not be colocated

Docs

@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Dec 15, 2020
@knative-prow-robot knative-prow-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Dec 15, 2020
@arghya88 arghya88 changed the title set antiaffinity for receiver deployment Set antiaffinity for receiver deployment Dec 15, 2020
@arghya88 arghya88 changed the title Set antiaffinity for receiver deployment Set anti-affinity for receiver deployment Dec 15, 2020
@codecov
Copy link

codecov bot commented Dec 15, 2020

Codecov Report

Merging #483 (2a57f90) into master (17e3199) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #483   +/-   ##
=========================================
  Coverage     76.79%   76.79%           
  Complexity      269      269           
=========================================
  Files            59       59           
  Lines          1969     1969           
  Branches         82       82           
=========================================
  Hits           1512     1512           
  Misses          342      342           
  Partials        115      115           
Flag Coverage Δ Complexity Δ
java-unittests 77.94% <ø> (ø) 0.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 17e3199...2a57f90. Read the comment docs.

Copy link
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

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

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 15, 2020
@pierDipi
Copy link
Member

Can you add a release note? Something like:

Receivers now specify anti-affinity so that replicas will not be colocated.

/kind enhancement

Signed-off-by: Arghya Sadhu <arghya88@gmail.com>
Copy link
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

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

Thank you!

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 15, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arghya88, pierDipi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot merged commit 422c896 into knative-extensions:master Dec 15, 2020
@arghya88 arghya88 deleted the receiver-antiaffinity branch December 15, 2020 13:32
pierDipi pushed a commit to pierDipi/eventing-kafka-broker that referenced this pull request Feb 27, 2021
Signed-off-by: Arghya Sadhu <arghya88@gmail.com>
pierDipi added a commit to pierDipi/eventing-kafka-broker that referenced this pull request Nov 30, 2022
…sions#2773) (knative-extensions#483)

Since we create the contract ConfigMaps in the Consumer reconciler
but the scheduler is called in the ConsumerGroup reconciler and it
fails with "not enough pod replicas" when the data plane pods are
in pending state.

This is not evident in our CI but it might be a signal of an edge
case caused by a certain sequence of events.

In this PR, I'm creating ConfigMaps before calling the scheduler
in the ConsumerGroup reconciler so that the pods can become
ready before the scheduler verifies which pods are available
to schedule vpods.

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/data-plane cla: yes Indicates the PR's author has signed the CLA. kind/enhancement lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Receiver deployments should use anti affinity
3 participants