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.

Sign up for GitHub

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

Jump to bottom

Allow users to easily see expiring harvester cloud credentials and to renew them #11332

Open
Tracked by #11256
github-actions bot opened this issue Jul 2, 2024 · 3 comments · May be fixed by #12157
Open
Tracked by #11256

Allow users to easily see expiring harvester cloud credentials and to renew them #11332

github-actions bot opened this issue Jul 2, 2024 · 3 comments · May be fixed by #12157
Assignees
@richard-cox
Labels
kind/enhancement priority/0 QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/5 Size Estimate 5
Milestone
v2.10.0

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jul 2, 2024 •
edited by richard-cox
Loading

Epic: #11256 SURE-8516

This is a forwardport issue for #11270, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

Requires expiring label on cloud cred

  • Global notification somewhere warning of expired / soon to expire harv cloud creds
  • Clearly see in cloud cred table expired / soon to expire (see cluster dashboard certs list for pattern?)
    • Column for sorting, only if harv cloud cred present?
  • Sub row in harv clusters list to warn that cluster has a cloud cred that's expiring
  • Cloud Cred bulk action to renew (recreate kubeconfig, update cloud cred)

Edit: Blocked on rancher/rancher#47241
@github-actions github-actions bot added kind/enhancement priority/0 QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None labels Jul 2, 2024
@github-actions github-actions bot added this to the v2.10.0 milestone Jul 2, 2024
@nwmac nwmac modified the milestones: v2.10.0, v2.11.0 Jul 4, 2024
@gaktive gaktive modified the milestones: v2.11.0, v2.10.0 Jul 4, 2024
@gaktive
Copy link
Member

gaktive commented Jul 16, 2024

Leaving this as the 2.10.0 version since this was the forward port. Making the other one the backport but I'll emphasize that this ticket should be worked on first.

@gaktive gaktive mentioned this issue Jul 16, 2024
Open
@gaktive
Copy link
Member

gaktive commented Jul 16, 2024 •
edited
Loading

This needs to line up with Harvester 1.4.0 which is set to come out before 2.10.0.

@gaktive gaktive changed the title [forwardport v2.10.0] Allow users to easily see expiring harvester cloud credentials and to renew them Allow users to easily see expiring harvester cloud credentials and to renew them Jul 31, 2024
@gaktive gaktive added size/5 Size Estimate 5 and removed QA/None labels Jul 31, 2024
@richard-cox richard-cox mentioned this issue Aug 7, 2024
Open
4 tasks
@snasovich snasovich mentioned this issue Sep 24, 2024
Open
@richard-cox richard-cox mentioned this issue Sep 25, 2024
Open
@richard-cox
Copy link
Member

Update Train

Note - each issue is linked to a backport

@richard-cox richard-cox mentioned this issue Sep 25, 2024
Closed
@richard-cox richard-cox self-assigned this Sep 25, 2024
@richard-cox richard-cox linked a pull request Oct 7, 2024 that will close this issue
Open
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@richard-cox richard-cox

Labels
kind/enhancement priority/0 QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/5 Size Estimate 5
Projects
None yet
Milestone
v2.10.0
3 participants
@nwmac @gaktive @richard-cox