Brad Davidson
Brad Davidson
We don't really use that CRD, since the helm controller is usually deployed embedded in RKE2 or K3s, and it will create the CRDs itself using the correct version of...
Hmm, fair enough it may need some additional modifications for more recent versions of Kubernetes. What are you trying to accomplish? If you run the controller it will generate and...
You don't need to install the CRD to deploy the controller. As I said above, the CRD will be created by the controller when it first starts up. I'll leave...
I've opened a PR to add a CRD release artifact, in the mean time you can use this: ```yaml apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition metadata: name: helmcharts.helm.cattle.io spec: group: helm.cattle.io names:...
Sorry, couple typos in there. Updated the comment, please try again.
Kine has the capability to tune the connection pooling parameters, but we have not yet exposed these options as k3s command-line flags.
No, we're not using that library. We're using github.com/lib/pq.
I took a shot at improving compaction performance with the most recent round of updates but I don't think we've baseline benchmarked database performance. Can I ask for more info...
Are you just looking at database connections and connection rate to gauge performance? Are you evaluating any of the apiserver datastore performance metrics that it exposes for collection by Prometheus?
@guangxuli take a look at https://github.com/rancher/k3s/issues/1575#issuecomment-722674596 if you would.