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

cluster-autoscaler:1.29.3 not yet present #68047

Closed
nhumphreys opened this issue Jun 24, 2024 · 5 comments
Closed

cluster-autoscaler:1.29.3 not yet present #68047

nhumphreys opened this issue Jun 24, 2024 · 5 comments
Assignees
Labels
cluster-autoscaler solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@nhumphreys
Copy link

Name and Version

bitnami/cluster-autoscaler

What architecture are you using?

None

What steps will reproduce the bug?

I wish to run the latest 1.29 series cluster-autoscaler on my 1.29 kubernetes cluster

What is the expected behavior?

Expect to find 1.29.3 available

What do you see instead?

1.29.2 is the latest at this time

Additional information

No response

@nhumphreys nhumphreys added the tech-issues The user has a technical issue about an application label Jun 24, 2024
@github-actions github-actions bot added the triage Triage is needed label Jun 24, 2024
@carrodher
Copy link
Member

Unfortunately, 1.29.3 was not released on our side given that it was released upstream close to the new minor version. Our automated test & release pipeline released 1.30.0 right after 1.29.2.

@nhumphreys
Copy link
Author

thanks, does that mean that the automated pipeline will be instructed to release 1.29.3?

@carrodher
Copy link
Member

thanks, does that mean that the automated pipeline will be instructed to release 1.29.3?

No, we don't release versions retroactively. The last version of 1.29.x will be 1.29.2. From that moment, new versions will appear sequentially, but not previous ones. That version in the upstream won't be present in Bitnami.

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Jul 11, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cluster-autoscaler solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants