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

Fixed affinity and tolerations helm chart issue #34

Merged
merged 8 commits into from
Apr 2, 2020

Conversation

viperKiran
Copy link
Contributor

I have found affinity and tolerations in deployments are indented wrongly and added Pod Disruption Budget template for keda and metrics.

tomkerkhove and others added 6 commits March 31, 2020 17:23
* Provide capability to specify annotations in Helm chart

Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>

* Use podAnnotations for metricsAdapter / keda

Signed-off-by: kiran <kiran.sundaravarathan@paytm.com>
Signed-off-by: kiran <kiran.sundaravarathan@paytm.com>
* Add priorityClassName to pods specs

Signed-off-by: Amir Schwartz <amschwar@microsoft.com>

* Increment chart version

Signed-off-by: Amir Schwartz <amschwar@microsoft.com>

Co-authored-by: Amir Schwartz <amschwar@microsoft.com>
Signed-off-by: kiran <kiran.sundaravarathan@paytm.com>
…ic-apiserver

Signed-off-by: kiran <kiran.sundaravarathan@paytm.com>
Signed-off-by: kiran <kiran.sundaravarathan@paytm.com>
Signed-off-by: kiran <kiran.sundaravarathan@paytm.com>
Copy link
Member

@tomkerkhove tomkerkhove left a comment

Choose a reason for hiding this comment

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

LGTM

@tomkerkhove
Copy link
Member

Since it's shipping a new version it would be good to have @ahmelsayed his signoff as well

@tomkerkhove
Copy link
Member

Actually I would suggest not to ship a new version yet and waith for new release cycle

@viperKiran
Copy link
Contributor Author

Thanks, @tomkerkhove for approving this. I am wondering about the merge conflict since I don't have write access. Will maintainers take care of it?

@tomkerkhove
Copy link
Member

That's actually something you can fix by merging master in your branch and fixing the conflicts.

Would you mind removing the changes that ship a new version as well please?

@viperKiran
Copy link
Contributor Author

@tomkerkhove Done as you wish. Let me know if you have any concerns.

@tomkerkhove
Copy link
Member

LGTM, thanks for the contribution @viperKiran!

@tomkerkhove tomkerkhove merged commit 9963179 into kedacore:master Apr 2, 2020
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.

4 participants