-
Notifications
You must be signed in to change notification settings - Fork 2
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Deleted projects leave orphaned Instances/WorkloadDeployments and never-ending projector errors
bugSomething isn't workingSomething isn't workingStatus: Open.#194 In datum-cloud/compute;Management controllers re-reconcile idle workloads in a loop (no metric visibility)
bugSomething isn't workingSomething isn't workingStatus: Open.#191 In datum-cloud/compute;Design a service-provider view into workload health and consumer troubleshooting for compute
enhancementNew feature or requestNew feature or requestStatus: Open.#183 In datum-cloud/compute;Handle project suspension in the compute service (non-destructive pause/resume)
documentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestUrgentPriority: UrgentStatus: Open.- Status: Open.#175 In datum-cloud/compute;
- Status: Open.#174 In datum-cloud/compute;
Decide whether compute workloads support anonymous (credential-less) image pulls
UrgentPriority: UrgentStatus: Open.- Status: Open.#164 In datum-cloud/compute;
- Status: Open.#163 In datum-cloud/compute;
Shared ConfigMaps/Secrets only reach one location when workloads span multiple cities
HighPriority: HighStatus: Open.#155 In datum-cloud/compute;- Status: Open.
Define an authoritative instance-type resource catalog (single source of truth for vCPU/memory)
LowPriority: LowStatus: Open.#137 In datum-cloud/compute;