Skip to main content
Coming in the first release. This page describes behaviour being built for the first Gliss release. Details may change before it ships.
A diagnosis links here when pods stay Pending because no node has enough free CPU or memory, for example:
If you are a builder: this is not your app’s problem, and your AI cannot fix it. Tell your IT team or the maintainer named in the diagnosis. If you maintain the platform: raise the node group’s maximum size, or add capacity through a platform release. Check whether one app’s requests grew unexpectedly before adding nodes.