[I] Helm chart is too big to be installed through rancher manager [pulsar-helm-chart]

["edonin (via GitHub)" <gi...@apache.org>]

edonin opened a new issue, #621:
URL: https://github.com/apache/pulsar-helm-chart/issues/621

   **Describe the bug**
   Since version 4.0.0 pulsar helm chart is too big (> 1 MB), and it makes it impossible to install through Rancher Manager
   
   **To Reproduce**
   If you try to install pulsar 4.1.0 through rancher manager interface, you will have an error raised:
   
   message=Secret "helm-operation-2cbbx" is invalid: data: Too long: must have at most 1048576 bytes
   
   **Additional context**
   Rancher is storing the helm chart tar ball in a secret, nevertheless, since victoria metrics dependency was added, the size of the helm tar ball has increased to be bigger now than 1 MB. And in kubernetes, by default, secret cannot be bigger than 1 MB, so it is cannot be installed.
   
   <img width="639" height="84" alt="Image" src="https://github.com/user-attachments/assets/257a5789-78b3-4fc7-b65c-47d8678933a3" />
   
   <img width="1078" height="239" alt="Image" src="https://github.com/user-attachments/assets/a7eb35bc-0ff9-47cf-8b2e-913728496342" />


-- 
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: commits-unsubscribe@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Helm chart is too big to be installed through rancher manager [pulsar-helm-chart]

["lhotari (via GitHub)" <gi...@apache.org>]

lhotari commented on issue #621:
URL: https://github.com/apache/pulsar-helm-chart/issues/621#issuecomment-3108090406

   As a workaround, you could push the Apache Pulsar Helm chart to a OCI registry and use that in Rancher.
   Helm for OCI registries reference can be found at https://helm.sh/docs/topics/registries/.
   
   For example, this is how I accomplished pushing to OCI registry:
   ```
   wget https://downloads.apache.org/pulsar/helm-chart/4.1.0/pulsar-4.1.0.tgz
   helm push pulsar-4.1.0.tgz oci://docker.io/lhotari
   ```
   
   this is the result: https://hub.docker.com/layers/lhotari/pulsar/4.1.0/images/sha256-8ea593fd05cc52737200a95104534d87f17f6ed3fbd111d0fdd7e286dcfdf38c
   
   We could start pushing Apache Pulsar Helm chart releases to Docker Hub so that this workaround wouldn't be needed. However, one of the problems is that we cannot use the existing "apachepulsar" Docker Hub account, since we already use the name "pulsar" for actual Pulsar images. Docker Hub doesn't allow multi-level paths for image name (https://github.com/docker/hub-feedback/issues/1404). Helm OCI support requires that the image name after the "namespace" matches the chart name. Since it's already "pulsar", that's why "apachepulsar" cannot be used.
   
   


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org