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

FIX: Modifying the helm chart used for Pinot Quickstart #14952

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

subhashini-26
Copy link

This bugfix fixes the issue with #14696

The following error is encountered when trying to deploy Apache Pinot on k8s clusters using Helm chart with the instructions mentioned here:
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: Namespace "pinot-quickstart" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "[app.kubernetes.io/managed-by](http://app.kubernetes.io/managed-by)": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "pinot"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "pinot-quickstart"

The fix here removes the additional namespace.yaml present in the templates, which is redundant when the user does the namespace creation manually, as provided in the quickstart documentation.

bugfix kubernetes

The program was tested solely for our own use cases, which might differ from yours.

Signed-off-by: Subhashini Narayanaswamy [email protected] on behalf of Mercedes-Benz Research and Development India

https://github.com/mercedes-benz/mercedes-benz-foss/blob/master/PROVIDER_INFORMATION.md

This bugfix fixes the issue with apache#14696

According to the documentation for installation of Pinot in k8s using helm charts (https://docs.pinot.apache.org/basics/getting-started/kubernetes-quickstart#start-pinot-with-helm), the namespace is created manually. This creates a conflict with the namespace.yaml present in the templates, leading to failure of deployment.

Signed-off-by: Subhashini Narayanaswamy  <[email protected]>
@Jackie-Jiang
Copy link
Contributor

@abhioncbr Can you help review this?

@codecov-commenter
Copy link

codecov-commenter commented Jan 30, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.70%. Comparing base (59551e4) to head (a3143e1).
Report is 1652 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #14952      +/-   ##
============================================
+ Coverage     61.75%   63.70%   +1.95%     
- Complexity      207     1472    +1265     
============================================
  Files          2436     2710     +274     
  Lines        133233   151924   +18691     
  Branches      20636    23463    +2827     
============================================
+ Hits          82274    96783   +14509     
- Misses        44911    47871    +2960     
- Partials       6048     7270    +1222     
Flag Coverage Δ
custom-integration1 100.00% <ø> (+99.99%) ⬆️
integration 100.00% <ø> (+99.99%) ⬆️
integration1 100.00% <ø> (+99.99%) ⬆️
integration2 0.00% <ø> (ø)
java-11 63.68% <ø> (+1.97%) ⬆️
java-21 63.57% <ø> (+1.95%) ⬆️
skip-bytebuffers-false 63.70% <ø> (+1.95%) ⬆️
skip-bytebuffers-true 63.56% <ø> (+35.83%) ⬆️
temurin 63.70% <ø> (+1.95%) ⬆️
unittests 63.70% <ø> (+1.95%) ⬆️
unittests1 56.23% <ø> (+9.34%) ⬆️
unittests2 34.01% <ø> (+6.28%) ⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

3 participants