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
I'm following the Quickstart guide and encounter a problem during deployment. There are two pods keep CrashLoopBackOff. The rest is running, as shown below:
In dashboard, pods list:
Then after reviewing some previous issues, seems the failing is caused by the ARM architecture.
Hence, I have moved to an Intel chip machine and all the pods work now, but after I installed them with helm, there is no Policy is available for creating DT instances and types. After I check the log in the log in that page, seems it is caused by the bad request 400 of the get policies request for extended-api for ditto. I wonder if that is caused by the Mongo connection, as it is enabled by getAllpolicies_enabled.
The text was updated successfully, but these errors were encountered:
Hi,
I'm following the Quickstart guide and encounter a problem during deployment. There are two pods keep CrashLoopBackOff. The rest is running, as shown below:
In dashboard, pods list:
Then after reviewing some previous issues, seems the failing is caused by the ARM architecture.
Hence, I have moved to an Intel chip machine and all the pods work now, but after I installed them with helm, there is no Policy is available for creating DT instances and types. After I check the log in the log in that page, seems it is caused by the bad request 400 of the get policies request for extended-api for ditto. I wonder if that is caused by the Mongo connection, as it is enabled by getAllpolicies_enabled.
The text was updated successfully, but these errors were encountered: