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

add resource requests and limits to airbyte minio container #273

Open
wants to merge 21 commits into
base: main
Choose a base branch
from

Conversation

machariamuguku
Copy link

What

How

  • Add optional resource requests and limits configs to main helm chart

Recommended reading order

  1. minio.yaml
  2. values.yaml
  3. README.md

Can this PR be safely reverted / rolled back?

  • YES 💚
  • NO ❌

🚨 User Impact 🚨

Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.

@machariamuguku
Copy link
Author

Note:

  • The ref link (ref: http://kubernetes.io/docs/user-guide/compute-resources/) is broken
  • Likely moved to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
  • The same is referred to in many other places within the charts and thus can easily be found in case of global replace

Copy link

sonarqubecloud bot commented Dec 5, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
1.7% 1.7% Duplication

@CLAassistant
Copy link

CLAassistant commented Mar 6, 2024

CLA assistant check
All committers have signed the CLA.

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
1.2% Duplication on New Code

See analysis details on SonarCloud

machariamuguku and others added 3 commits March 22, 2024 15:32
## What

* Makes git ignore [`jenv`](https://www.jenv.be/)'s .`.java-version`
file, to avoid adding it as an unintended artifact in future commits
* As of now, we do not explicitly encourage saving this file, nor do we
require [`jenv`](https://www.jenv.be/) to contribute to the project,
indicating that [`jenv`](https://www.jenv.be/) is the responsibility of
the user, instead of the maintainer(s)

## How

* Adds a rule to the project-level .gitignore file to ignore all
.java-version files

## Recommended reading order
1. Related to the initial steps in
[developing-locally](https://docs.airbyte.com/contributing-to-airbyte/resources/developing-locally)

## Can this PR be safely reverted and rolled back?
<!--
* If you know that your be safely rolled back, check YES.*
* If that is not the case (e.g. a database migration), check NO.
* If unsure, leave it blank.*
-->
- [ x ] YES 💚
- [ ] NO ❌
@machariamuguku
Copy link
Author

@perangel you seem to have started working on this. Any update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Helm Chart: Add kubernetes resource requests and limits for airbyte minio container
4 participants