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
The changes to password references introduced in #356 (and #364) introduced a regression where a "standard" installation as described in the docs is no longer working.
The relevant pods now try to resolve a password key that doesn't exist anymore:
`Events:
Type Reason Age From Message
Normal Scheduled 25s default-scheduler Successfully assigned default/nautobot-default-5b64b5d685-6wc8t to minikube
Normal Pulled 22s kubelet Successfully pulled image "ghcr.io/nautobot/nautobot:2.0.5-py3.11" in 1.103s (2.103s including waiting)
Warning Failed 7s (x2 over 22s) kubelet Error: couldn't find key NAUTOBOT_REDIS_PASSWORD in Secret default/nautobot-redis`
This happens for redis, postgresql and probably mariadb as well.
I have a fix coming soon.
The text was updated successfully, but these errors were encountered:
The changes to password references introduced in #356 (and #364) introduced a regression where a "standard" installation as described in the docs is no longer working.
The relevant pods now try to resolve a password key that doesn't exist anymore:
`Events:
Type Reason Age From Message
Normal Scheduled 25s default-scheduler Successfully assigned default/nautobot-default-5b64b5d685-6wc8t to minikube
Normal Pulled 22s kubelet Successfully pulled image "ghcr.io/nautobot/nautobot:2.0.5-py3.11" in 1.103s (2.103s including waiting)
Warning Failed 7s (x2 over 22s) kubelet Error: couldn't find key NAUTOBOT_REDIS_PASSWORD in Secret default/nautobot-redis`
This happens for redis, postgresql and probably mariadb as well.
I have a fix coming soon.
The text was updated successfully, but these errors were encountered: