Open drawnwren opened 6 months ago
Swapping pulsar for kafka fixes the problem, but that doesn't seem like a complete solution.
looks like a bug
em... I can't reproduce it by using helm directly. Seems to me a bug of https://fluxcd.io/
I have the same exact issue using FluxCD v2. I can follow up with more details if required. Going to attempt to use a postRenderer to resolve
After rendering the template locally, I found the offending resource:
helm template miluvs zilliztech/milvus
Note: I'm not using any custom values
Output Snippet:
apiVersion: v1
kind: ConfigMap
metadata:
name: "milvus-pulsar-proxy"
namespace: default
labels:
app: pulsar
chart: pulsar-2.7.8
release: milvus
heritage: Helm
cluster: milvus-pulsar
component: proxy
data:
clusterName: milvus-pulsar
httpNumThreads: "8"
statusFilePath: "/pulsar/status"
# prometheus needs to access /metrics endpoint
webServicePort: "80"
servicePort: "6650"
brokerServiceURL: pulsar://milvus-pulsar-broker:6650
brokerWebServiceURL: http://milvus-pulsar-broker:8080
# Authentication Settings
PULSAR_GC: |
-XX:MaxDirectMemorySize=2048m
PULSAR_MEM: |
-Xms2048m -Xmx2048m
httpNumThreads: "100"
This is due to a hardcoded value here: https://github.com/apache/pulsar-helm-chart/blob/pulsar-2.7.8/charts/pulsar/templates/proxy-configmap.yaml#L31C1-L31C22
Later versions of the pulsar helm chart does not include this hardcoded value.
I was unable to resolve with postrenderers, but using flat yaml via flux will probably work (if you update the rendered manifest by removing the duplicate key).
When using 4.1.17 w/ flux I get the following error:
Here are the values I'm passing