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

Release 1.2 #333

Merged
merged 270 commits into from
Jan 22, 2025
Merged

Release 1.2 #333

merged 270 commits into from
Jan 22, 2025

Conversation

keyvaann
Copy link
Collaborator

@keyvaann keyvaann commented Oct 9, 2024

We can use this branch to make the new release.

keyvaann and others added 30 commits May 2, 2024 12:58
Fixed radar-push-endpoint servicemonitor
* dev:
  bugfix: BackOffLimitExceeded GLIBC not found Velero
  Update velero version to fix BackfOffLimit error
  Fixed radar-push-endpoint servicemonitor
* dev:
  bugfix: BackOffLimitExceeded GLIBC not found Velero
  Update velero version to fix BackfOffLimit error
  Fixed radar-push-endpoint servicemonitor
  Upgrade catalog server to chart 0.5.2
Update chart versions for egress config fixes
PR feedback Keyvan.
PR feedback Keyvan.
PR feedback Keyvan.
@@ -19,7 +17,6 @@ resources:
ingress:
enabled: true
annotations:
kubernetes.io/ingress.class: nginx
Copy link
Member

Choose a reason for hiding this comment

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

Do we need to replace this with ingressClassName: "nginx"?

Copy link
Collaborator Author

@keyvaann keyvaann Nov 17, 2024

Choose a reason for hiding this comment

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

Yes but it is in the latest version of the schema registry helm chart so there shouldn't be an issue.
RADAR-base/cp-helm-charts@44e0148

Copy link
Member

Choose a reason for hiding this comment

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

Oh okay thank you! Is it 0.3.2?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes!

@Hsankesara Hsankesara mentioned this pull request Dec 4, 2024
@keyvaann
Copy link
Collaborator Author

keyvaann commented Jan 13, 2025

@pvannierop @mpgxvii @yatharthranjan
I think it's time to merge this PR and I need approval to make the release. Please let me know if you want to make further adjustments.

Copy link
Member

@yatharthranjan yatharthranjan left a comment

Choose a reason for hiding this comment

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

Thanks LGTM.

It would be nice if @mpgxvii and @baixiac can review too.

I assume the release version would be 1.2.0, not 1.2 ?

Copy link
Member

@baixiac baixiac left a comment

Choose a reason for hiding this comment

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

Nice work. Just wonder if it's worth mentioning this release will continue supporting K8s 1.29 and 1.28. Also, can the README link back to RADAR-K8s-Infrastructure as an alternative for users preferring a cloud provider over k3s?

etc/base.yaml Outdated Show resolved Hide resolved
etc/base.yaml Outdated Show resolved Hide resolved
@keyvaann
Copy link
Collaborator Author

Nice work. Just wonder if it's worth mentioning this release will continue supporting K8s 1.29 and 1.28. Also, can the README link back to RADAR-K8s-Infrastructure as an alternative for users preferring a cloud provider over k3s?

I did add the note about RADAR-K8s-Infrastructure, I think mentioning older versions of K8S isn't needed as I don't think there will be new installations that are using it.

@keyvaann keyvaann merged commit ef5ae91 into main Jan 22, 2025
3 checks passed
@keyvaann keyvaann deleted the release-1.2 branch January 23, 2025 09:18
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.

8 participants