Facing linkerd issue (NOT valid ERROR)

[SarangBS]

Hey everyone,
I am encountering the following error in connectivity to linkerd:

ERROR ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}: linkerd_proxy_identity_client::certify: Failed to obtain identity error=invalid peer certificate: NotValidYet
[   150.015736s]  WARN ThreadId(01) linkerd_app: Waiting for identity to be initialized...
[   150.044949s]  INFO ThreadId(01) linkerd_proxy::signal: received SIGTERM, starting shutdown
[   150.044965s]  INFO ThreadId(01) linkerd2_proxy: Received shutdown signal
[   150.139443s]  INFO ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}:controller{addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}: linkerd_pool_p2c: Adding endpoint addr=10.23.24.154:8080
[   150.139474s]  INFO ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}:controller{addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}: linkerd_pool_p2c: Adding endpoint addr=10.23.26.105:8080
[   150.139480s]  INFO ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}:controller{addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}: linkerd_pool_p2c: Adding endpoint addr=10.23.25.51:8080
[   150.145762s] ERROR ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}: linkerd_proxy_identity_client::certify: Failed to obtain identity error=invalid peer certificate: NotValidYet

i have also confirmed that the certificate is not expired, but we still see this NotValidYet error. The pods are unable to obtain a valid identity and failing the connectivity.

whenever i deploy the services or do the new build for services the pods fail to connect to linkerd due to above issue .
Has anyone encountered this sought of issue .
Needed some help debugging the issue .

[alpeb]

Can you check the "Not Before" field in the cert? Maybe it has an invalid value?