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
{{ message }}
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.
Currently when microk8s and minikube local k8s are running simultaneously then status checks are not correct as we dont force kubectl config set-context when performing status checks.
Similarly, if our db is initialized with microk8s then the data fro minikube will not work. This can be solved by separating database for microk8s and minikube like we did for minio buckets.
Also, this PR can move k8s db and minio from engine code to cc.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently when microk8s and minikube local k8s are running simultaneously then status checks are not correct as we dont force
kubectl config set-context
when performing status checks.Similarly, if our db is initialized with microk8s then the data fro minikube will not work. This can be solved by separating database for microk8s and minikube like we did for minio buckets.
Also, this PR can move k8s db and minio from engine code to cc.
The text was updated successfully, but these errors were encountered: