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 prometheus federator app version to 0.3.5 / charts to 0.4.1 #81

Merged
merged 3 commits into from
Dec 15, 2023

Conversation

alexandreLamarre
Copy link
Contributor

Related Issue:

Checklist

Please fill out this table to identify which fields need to be modified in your PR.

Under Status, either indicate Does Not Apply or Added to this PR.

Version to be incremented Why should this be modified? Status
version in rancher-project-monitoring package.yaml You modified the contents of the rancher-project-monitoring chart to make changes Added in this PR
helmProjectOperator.image.tag in prometheus-federator values.yaml Either you modified the rancher-project-monitoring chart or you modified the main.go file Does Not Apply
appVersion in prometheus-federator Chart.yaml You modified the helmProjectOperator.image.tag in the above box Added in this PR
version in prometheus-federator Chart.yaml Either you modified the appVersion in the above box or you modified the contents of the prometheus-federator chart to make changes Added in this PR

update chart version to 0.4.1

pin upstream rancher-monitoring dep to 103.0.2-up45.31.1

Signed-off-by: Alexandre Lamarre <[email protected]>
Signed-off-by: Alexandre Lamarre <[email protected]>
@@ -58,7 +58,7 @@ helmProjectOperator:

image:
repository: rancher/prometheus-federator
tag: v0.3.4
tag: v0.3.5
Copy link
Contributor

@joshmeranda joshmeranda Dec 14, 2023

Choose a reason for hiding this comment

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

I don't think this tag exists? (same issue as above)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In the docs it mentions adding the git tag after a PR is merged, which didn't seem right but looking at how the automation works it seems that its fine

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Taking a look at past PRs, we are expected to tag the merge commit as the release version, CI runs with the a local $TAG option

Copy link
Contributor

@joshmeranda joshmeranda left a comment

Choose a reason for hiding this comment

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

See comments, just a versioning issue

bump e2e ci go version to 1.20

Signed-off-by: Alexandre Lamarre <[email protected]>

enable shell tracing in e2e ci

Signed-off-by: Alexandre Lamarre <[email protected]>

debug versions in install rancher monitoring e2e ci

Signed-off-by: Alexandre Lamarre <[email protected]>

set helm version to v.3.13.1 in e2e ci

Signed-off-by: Alexandre Lamarre <[email protected]>
@alexandreLamarre alexandreLamarre marked this pull request as ready for review December 15, 2023 17:09
@alexandreLamarre alexandreLamarre merged commit 5a74d28 into main Dec 15, 2023
2 checks passed
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