Closed hhk7734 closed 7 months ago
@hhk7734 Knative operator now has to publish the artifacts in three ways: general yaml on the release page, operatorhub and the helm charts. The current structure is crucial for https://github.com/knative/operator/blob/main/hack/generate-bundle.sh, which is to generate the bundle to publish in operatorhub. I am wondering if you can take this into account as well to optimize the structure of the yamls.
I expect the generate-bundle.sh
script to work just fine, since I'm aiming to create config/**
from config/charts
as is. I'll work on it as soon as I have time and make a PR, so please review again then.
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
.
Problem The current chart is generated by
hack/generate-helm.sh
, which makes it difficult to modify the Helm template.Therefore, I propose generating the base files used for Kustomize from the chart, in the opposite way of the current method.
Persona: System Operator
Exit Criteria Pass existing CI tests using helm chart and kustomize
Time Estimate (optional): 1 developer, 1~2 days
After changes