pulsar-helm-chart
pulsar-helm-chart copied to clipboard
replace handmade release script with official action
This refers to #290.
The helm/chart-releaser-action
update index.yaml
in an incremental manner, so we need to push the existing index.yaml
file to gh-pages
later.
cc @michaeljmarshall @ericsyh @mattisonchao @yaalsn
@michaeljmarshall Thanks for your follow-up. Let me check your investigation today and feedback. My first object is to decouple the Chart index file from the website :)
@tisonkun - where do you think we should host it? One concern with moving it is that helm repo update
will break.
will break
Yep. As mentioned in #290, we can set a server-side redirection in the website .htaccess
. The reason is that, website build process doesn't handle Chart yaml index so that it's possible we accidentally remove the file - they're totally different topics.
Setting up a redirection is in the domain of a website maintenance and avoid further development accidentally modifies it.
Sure, I agree that the current workflow is a bit of a hack, and the current index.yaml
is not very well protected. I added a comment to #290, too.
@michaeljmarshall I've narrow the scope to replace the lint scripts with chart-testing-action
. PTAL.
I'm going through your proposal on release process now.
Weird. Is it an unstable test?
@michaeljmarshall I don't think the failures are related to this patch. Could you take a looks and rerun the tests?
@tisonkun - yes, the TLS Installation and ZK & BK TLS Only tests are unstable. I have spent some time looking into them this week, but I haven't found the root cause. It seems like there may be some instability with the environment because some of the errors are about refused connections to ports that appear to be working for some pods but not others.
Here is an issue for the flaky tests: #311