Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update deps for the release process. #4529

Merged
merged 4 commits into from
Mar 30, 2022

Conversation

absoludity
Copy link
Contributor

Signed-off-by: Michael Nelson minelson@vmware.com

Description of the change

Updates a bunch of deps following our release instructions. Also removes some notes in those instructions that I think are no longer necessary.

Benefits

Possible drawbacks

Applicable issues

  • fixes #

Additional information

Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
Comment on lines -69 to -102
### 0.3 - Development chart

Even though the official [Bitnami chart](https://github.com/bitnami/charts/tree/master/bitnami/kubeapps) is automatically able to retrieve the latest dependency versions, we still need to sync the versions declared in our own development chart.

#### 0.3.1 - Chart images

Currently, the [values.yaml](../../chart/kubeapps/values.yaml) uses the following container images:

- [bitnami/nginx](https://hub.docker.com/r/bitnami/nginx/tags)
- [bitnami/oauth2-proxy](https://hub.docker.com/r/bitnami/oauth2-proxy/tags)

> As part of this release process, these image tags _must_ be updated to the latest minor version. In case of a major version, the change _should_ be tracked in a separate PR.

#### 0.3.2 - Chart dependencies

The chart [dependencies](../../chart/kubeapps/Chart.yaml) _must_ be checked to ensure the version includes the latest dependent charts.

- Check if the latest versions are already included by running:

```bash
helm dep list ./chart/kubeapps
```

- If they are not, run this other command to update the `requirements.lock` file:

```bash
# It requires Helm >=3.7.0, otherwise, just run `helm dep update ./chart/kubeapps`
helm repo update bitnami
helm dep update --skip-refresh ./chart/kubeapps
```

> As part of this release process, the chart dependencies _must_ be updated to the latest versions. In case of a major version, the change _should_ be tracked in a separate PR.

### 0.4 - Protobuf dependencies and autogenerated code
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've removed this section because we get this automatically from the merges of the bitnami chart now, don't we?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so. In the last 2-3 days we have received from Bitnami almost 1 chart update per day.

@castelblanque
Copy link
Collaborator

This PR covers the whole step 0 of release process document, right?
Thanks for the work!

@absoludity
Copy link
Contributor Author

This PR covers the whole step 0 of release process document, right? Thanks for the work!

Yep, except that I used yarn upgrade-interactive as per the updated docs.

@absoludity absoludity merged commit 17d4cab into vmware-tanzu:main Mar 30, 2022
@absoludity absoludity deleted the release-updates branch March 30, 2022 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants