Helm Chart

[owenthereal]

Problem

It would be nice that there is a helm chart for knative operator. Lots of companies make use of charts to install software into their clusters and an official chart is needed for this project.

Persona:
Which persona is this feature for?

Anyone using knative serving and/or eventing

Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.

A chart is implemented.

Time Estimate (optional):
How many developer-days do you think this may take to resolve?

N/A.

Additional context (optional)
Add any other context about the feature request here.

[houshengbo]

Is the chart used to install operator only, or install knative components, like serving or eventing?

[owenthereal]

Yes, this is the chart to install the operator which installs serving and/or eventing.

[abdennour]

• and configure them as well
  My full support to @owenthereal

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[ddelange]

/reopen

Or are there any other open threads on getting Helm support for Knative we can fold this one into?

I wanted to quickly try this stack out for running some autoscaling deployments, but ended up having to hack all sorts of values in the manifests to get it to run in our small cluster (lower memory limits, less cpu requests, we have tainted nodes so adding some tolerations, ... stuff that's usually configurable through helm).

Istio has helm charts ref, but knative.dev hosts custom Istio and Knative Istio controller manifests ref.

It would be much more convenient and maintainable to install the whole stack via helm (e.g. by default no networking layer, can enable one in helm values), probably with separate charts for CRDs.

[knative-prow]

@ddelange: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Or are there any other open threads on getting Helm support for Knative we can fold this one into?

I wanted to quickly try this stack out for running some autoscaling deployments, but ended up having to hack all sorts of values in the manifests to get it to run in our small cluster.

Istio has helm charts ref, but knative.dev hosts custom Istio and Knative Istio controller manifests ref.

It would be much more convenient and maintainable to install the whole stack via helm (e.g. by default no networking layer, can enable one in helm values), probably with separate charts for CRDs.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.