wsmoak opened a new issue, #14696:
URL: https://github.com/apache/pinot/issues/14696

   Following the instructions on 
https://docs.pinot.apache.org/basics/getting-started/kubernetes-quickstart
   
   Lead to the error:
   
   `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"`
   
   As discussed in 
https://apache-pinot.slack.com/archives/C01H1S9J5BJ/p1734789818814929
   
   Fasih Khatib provided the fix: 
   > You'll need to execute the following commands in your terminal after you 
create the pinot-quickstart namespace to import the namespace into Helm.
   
   ```
   export KIND=namespace
   export NAME=pinot-quickstart
   export RELEASE_NAME=pinot
   export NAMESPACE=pinot-quickstart
   kubectl annotate $KIND $NAME meta.helm.sh/release-name=$RELEASE_NAME
   kubectl annotate $KIND $NAME meta.helm.sh/release-namespace=$NAMESPACE
   kubectl label $KIND $NAME 
[app.kubernetes.io/managed-by=Helm](http://app.kubernetes.io/managed-by=Helm)
   ```
   
   Can these things be built into the Helm chart somehow?  If not they need to 
be in the instructions as additional commands to type.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to