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

[Bug] CRDs not included in artifact pull for 5.9.1 release #1561

Closed
ak185158 opened this issue May 28, 2024 · 4 comments · Fixed by #1562
Closed

[Bug] CRDs not included in artifact pull for 5.9.1 release #1561

ak185158 opened this issue May 28, 2024 · 4 comments · Fixed by #1562
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ak185158
Copy link

ak185158 commented May 28, 2024

Describe the bug
CRDs missing from 5.9.1 version of the grafana-operator manifests when using flux pull artifact

Version
v5.9.1

To Reproduce
Steps to reproduce the behavior:

  1. run flux pull artifact oci://ghcr.io/grafana/kustomize/grafana-operator:v5.9.1 --output ./grafana-operator/ to pull the manifests

Expected behavior
A clear and concise description of what you expected to happen.

Expected CRDs to be included as they were in previous releases, however they are absent with the 5.9.1 release version.

Suspect component/Location where the bug might be occurring
Please provide this if you know where this bug might occur otherwise leave as unknown

Screenshots
If applicable, add screenshots to help explain your problem.

Runtime (please complete the following information):

  • OS: [e.g. Linux,Fedora,Mac]
  • Grafana Operator Version [e.g. v5.0.0]
  • Environment: [e.g Openshift,Kubernetes,minikube etc. please specify versions]
  • Deployment type: [e.g Openshift OLM/Helm/kustomize]
  • Other: [Other variables/things that might be relevant to this bug, versions of other services e.g. operator-sdk]

Additional context
Add any other context about the problem here.

@ak185158 ak185158 added bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 28, 2024
@weisdd weisdd added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 29, 2024
@weisdd
Copy link
Collaborator

weisdd commented May 29, 2024

Thanks for reporting this! #1562 aims to fix the flux artifact publishing process.

@weisdd
Copy link
Collaborator

weisdd commented May 29, 2024

We'll close it once the artifact for v5.9.1 is replaced

@weisdd
Copy link
Collaborator

weisdd commented Jun 3, 2024

@ak185158 We'll soon publish version v5.9.2 (@theSuess is already working on this), it should contain correct artifact this time. Sorry for the inconvenience!

@theSuess
Copy link
Member

theSuess commented Jun 3, 2024

v5.9.2 is now released and pullable via flux!

@theSuess theSuess closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
3 participants