You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to deploy my helm chart using fleet.yaml file. I get this error from the gitJob pod:
level=fatal msg="rpc error: code = ResourceExhausted desc = trying to send message larger than max (2487345 vs. 2097152)"
Expected Behavior
Pulling the helm chart and deploying to the target clusters
Steps To Reproduce
Install rancher and fleet
add a git repository
add to the repository a fleet.yaml file that directs to helm chart using "oci" url
Environment
- Architecture: x86_64 GNU/Linux
- Fleet Version: v0.9.4
- Cluster: (The issue is before the binding to the cluster, so I believe these are less important)
- Provider: EKS
- Options: 14 nodes, storageclasses and loadbalancer are defined
- Kubernetes Version: 1.29
@moriahpopo maybe this will help you, in case you're deploying multiple versions of your chart in multiple clusters. Fleet seems to bundle all files needed from the chart in the Bundle object, which can make it way to big for the k8s API to handle. Please also check that you don't have any binaries/ sizeable files in your repository, as they are unfortunately also added to the bundle.
If you do, you could try excluding them using a .fleetignore file. Maybe that will do the trick ;)
@puffitos Thanks for your comment.
This is not the issue here. I don't have metadata or other files that I don't need as part of the deployment.
In addition, I'm getting this error when I'm trying to deploy one version for only one cluster.
Is there an existing issue for this?
Current Behavior
I'm trying to deploy my helm chart using fleet.yaml file. I get this error from the gitJob pod:
level=fatal msg="rpc error: code = ResourceExhausted desc = trying to send message larger than max (2487345 vs. 2097152)"
Expected Behavior
Pulling the helm chart and deploying to the target clusters
Steps To Reproduce
Environment
Logs
Anything else?
I'm deploying this chart using Helm (v3.9.0). It is working well, and the grpc is not an issue.
Let me know if more logs can help.
Thank you
The text was updated successfully, but these errors were encountered: