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
However, there is a potential issue where a worker node may cache an already expired certificate. The expired certificate would be stored at ~root/.akash/k8s-config/provider.pem on the worker node. This becomes especially problematic when there are multiple worker nodes where the akash-provider pod could be deployed.
Therefore, it's advisable to also check for certificate expiration locally.
We are currently verifying if the certificate expires within the chain, as indicated in this section of the code - https://github.com/akash-network/helm-charts/blob/provider-4.3.7/charts/akash-provider/scripts/init.sh#L116.
However, there is a potential issue where a worker node may cache an already expired certificate. The expired certificate would be stored at
~root/.akash/k8s-config/provider.pem
on the worker node. This becomes especially problematic when there are multiple worker nodes where the akash-provider pod could be deployed.Therefore, it's advisable to also check for certificate expiration locally.
The workaround until then would be:
The text was updated successfully, but these errors were encountered: