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

Enable the proxy-injector to configure LINKERD2_PROXY_IDENTITY_*_REFRESH #13136

Open
Nuckal777 opened this issue Oct 4, 2024 · 0 comments
Open

Comments

@Nuckal777
Copy link

What problem are you trying to solve?

When the linkerd controlplane becomes unavailable the proxies fail to refresh their certificate. If the controlplane is unavailable for a sufficiently large duration, the proxy certificate actually expires, which causes all communication from/to meshed pods to fail. This includes the connection to the identity service, so a new certificate cannot be acquired. When this happens all affected pods need to be identified and restarted.

How should the problem be solved?

Enable the proxy-injector to set the following environment variables based on it's configuration:

  • LINKERD2_PROXY_IDENTITY_MIN_REFRESH
  • LINKERD2_PROXY_IDENTITY_MAX_REFRESH
    Both are already know to the proxy.

Any alternatives you've considered?

Currently, the lifetime of certificate by the identity service can be increased, but the certificate refresh is always scheduled at 70% of certificate lifetime. Depending one the required leeway certificate lifetimes increase significantly.

Lifetimes can be shortened again, when the refresh happens more often.

How would users interact with this feature?

Once the proxy-injector supports setting these environment variables, it would make sense to also expose the setting in the helm values.

Would you like to work on this feature?

maybe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant