You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The TLS certs for the agent hook last a year from what I can tell. Kudos to the Zarf devs as I have a cluster that has expired certs!
The issue I have was when I needed to update the TLS certs as the cluster breaks when the certs are invalid. Updating the certs is a bit tedious and manual. I'm hoping we can get a way for Zarf to automate the process, and, if possible detect and handle it automatically.
Describe the behavior you'd like
Given TLS certs have expired for the zarf agent hook
When the user zarf inits their cluster again
Then zarf detects the TLS certs have expired and renews them
Describe alternatives you've considered
The current solution I have is to manually update the zarf-state secret with new certs and zarf init the cluster again.
The steps I have:
run zarf tools gen-pki agent-hook.zarf.svc to generate a new crt, key, and ca file.
Update the zarf-state's agentTLS with the new ca, crt, and key.
run zarf init
restart agent-hook-xxxx pods
The text was updated successfully, but these errors were encountered:
Not sure if we would change the behavior to update certs on zarf init, will leave this open until a decision is made there. For now wanted to provide the command.
Is your feature request related to a problem? Please describe.
The TLS certs for the agent hook last a year from what I can tell. Kudos to the Zarf devs as I have a cluster that has expired certs!
The issue I have was when I needed to update the TLS certs as the cluster breaks when the certs are invalid. Updating the certs is a bit tedious and manual. I'm hoping we can get a way for Zarf to automate the process, and, if possible detect and handle it automatically.
Describe the behavior you'd like
zarf init
s their cluster againDescribe alternatives you've considered
The current solution I have is to manually update the zarf-state secret with new certs and
zarf init
the cluster again.The steps I have:
zarf tools gen-pki agent-hook.zarf.svc
to generate a new crt, key, and ca file.zarf init
The text was updated successfully, but these errors were encountered: