Closed andrestorresGL closed 2 years ago
The release workflow looks like it's intending to replace this: https://github.com/filecoin-project/helm-charts/blob/b8ef51d2dfd9bb2629c999e0383a0750e54392e1/.circleci/config.yml#L3-L35
Can you make sure this is feature compatible (missing helm lint)?
This PR will also need to delete the circle configuration to avoid the race to publish to github pages.
@andrestorresGL is there some background on the goals of triggering a helm upgrade for the release lotus-test
?
Specifically, some information on who is consuming the data from this release and if it's intended to catch bugs in the helm chart, test lotus releases, etc
@ognots this is a POC so you can configure and change later the K8 cluster target. The main goal is the deployment automation for new releases and allow the team to catch any bug.
@travisperson regarding the release proccess, yes the idea is replace the current, as I told @ognots this is a POC, so you may have to include additional behaviors that aren't present on this PR, I'll include the lint test and remove the current release process to avoid the publish race.
The main goal is the deployment automation for new releases and allow the team to catch any bug.
Which releases? Which team?
I'm going to close this, please reopen with additional details if this work is still wanted.
Adding GHA to publish a new release from master branch triggered by
filecoin-project/lotus
repo.release.yml
: GHA that creates a new Helm Chart and publish it as a github page. Secrets neededdeploy.yml
: triggered byrelease.yml
, this Action deploys the Helm Chart in a existing K8 cluster and waits until the helm release is up and running.Secrets needed.
.kube/config
file used if you don't want to connect to an EKS cluster.