Skip to content

[Merged by Bors] - Apply default resources to deployed Daemonset and Deployment#85

Closed
soenkeliebau wants to merge 8 commits intomainfrom
iss/default_resources
Closed

[Merged by Bors] - Apply default resources to deployed Daemonset and Deployment#85
soenkeliebau wants to merge 8 commits intomainfrom
iss/default_resources

Conversation

@soenkeliebau
Copy link
Copy Markdown
Member

Description

This PR introduces functionality to apply default resource limits to Deployments and Daemonsets when installing the helm chart.

It splits the configuration into two parameters for Deployment and DaemonSet and thus is marked as breaking because if someone defined resources in their values.yaml they would be applied to the Daemonset before this change, but would not be applied to it after this change.

It will not work as is, but needs to be rebased once the changes made in stackabletech/operator-templating#262 have been merged and rolled out to this repository via templating.

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes
# Author
- [ ] Changes are OpenShift compatible
- [ ] CRD changes approved
- [ ] Helm chart can be installed and deployed operator works
- [ ] Integration tests passed (for non trivial changes)
# Reviewer
- [ ] Code contains useful comments
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)
# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added

Once the review is done, comment bors r+ (or bors merge) to merge. Further information

Adds documentation to explain why the listener operator needs to run as root in its containers.
fixes #72
Split configuration into deployments and daemonsets.
@soenkeliebau soenkeliebau requested a review from nightkr June 28, 2023 13:16
soenkeliebau and others added 5 commits June 28, 2023 17:06
Co-authored-by: Natalie <teo@nullable.se>
…default_resources

# Conflicts:
#	deploy/helm/listener-operator/templates/controller-deployment.yaml
#	deploy/helm/listener-operator/templates/node-daemonset.yaml
#	deploy/helm/listener-operator/values.yaml
@soenkeliebau soenkeliebau requested a review from nightkr July 3, 2023 09:40
Copy link
Copy Markdown
Contributor

@nightkr nightkr left a comment

Choose a reason for hiding this comment

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

lgtm

@soenkeliebau
Copy link
Copy Markdown
Member Author

bors r+

bors bot pushed a commit that referenced this pull request Jul 3, 2023
# Description

This PR introduces functionality to apply default resource limits to Deployments and Daemonsets when installing the helm chart.

It splits the configuration into two parameters for Deployment and DaemonSet and thus is marked as breaking because if someone defined resources in their values.yaml they would be applied to the Daemonset before this change, but would not be applied to it after this change.

It will not work as is, but needs to be rebased once the changes made in stackabletech/operator-templating#262 have been merged and rolled out to this repository via templating.
@bors
Copy link
Copy Markdown

bors bot commented Jul 3, 2023

Pull request successfully merged into main.

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

@bors bors bot changed the title Apply default resources to deployed Daemonset and Deployment [Merged by Bors] - Apply default resources to deployed Daemonset and Deployment Jul 3, 2023
@bors bors bot closed this Jul 3, 2023
@bors bors bot deleted the iss/default_resources branch July 3, 2023 13:02
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