-
Notifications
You must be signed in to change notification settings - Fork 243
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
Rotate certificates for RKE2 provisioned clusters #4485
Comments
@snasovich I believe no UI changes will be needed if the backend includes To determine what actions are available, the UI looks at the
The actions for RKE1 clusters include the additional
To confirm that it would work if |
@catherineluse , based on the implementation PR rancher/rancher#36347 it doesn't look like that's how it's supported on backend as the changes seem to be limited to |
@catherineluse this is adding support for v2 clusters. v2 provisioning clusters are not supported in the v3 api. Steve does not support actions so the rotation will need to be triggered with a patch on the provisioning cluster through the v1 api
|
@paynejacob I noticed that when the UI does the cert rotation for RKE1 clusters, we set |
@catherineluse I forgot to update the ticket the |
Validating on v2.6-head commit
|
There's another thing that should be changed as well. The individual service list should be:
If the desire is to only have the ones currently listed, then at least the following need to be changed:
|
Oops, I didn't notice the service names are different in RKE2. I will change it to the full list. |
Validated using rke2
|
Confirmed with @catherineluse and @gaktive to add |
Detailed Description
![image](https://user-images.githubusercontent.com/85187633/139775023-31e8837e-bc46-4e83-ba7c-f8e451c96411.png)
The UI should provide an option to rotate certificates on RKE2 provisioned cluster, including an option to rotate certificates for an individual component. The UX should probably match what we have for RKE1 with context menu item and pop-up dialog asking to specify the settings:
Context
This is needed for RKE2 provisioning parity with RKE1
Additional Details
rancher/rancher#35343
The text was updated successfully, but these errors were encountered: