Skip to content

Commit d34534c

Browse files
committed
Added Project Idling and Account Pruning sections
1 parent a8f0abb commit d34534c

File tree

1 file changed

+25
-3
lines changed

1 file changed

+25
-3
lines changed

architecture/core_concepts/projects_and_users.adoc

Lines changed: 25 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -146,6 +146,28 @@ include any application objects for access by multiple projects, such as
146146
templates and images. These objects should be those that do not require
147147
communication between the pods.
148148

149-
150-
151-
149+
ifdef::openshift-online[]
150+
[[projects-idling]]
151+
== Project Idling
152+
In {product-title} Starter, a project that is inactive for more than 24 hours
153+
is idled. When a project's network activity falls below a configured threshold,
154+
a project is deemed inactive. When a project is idled, the replica count is set
155+
to `0` and all pods are deleted. All persistent volumes (PVs) and persistent
156+
volume claims (PVCs) in the project are left untouched. Upon receiving network
157+
traffic, the replica count will be scaled back to whatever it was before being
158+
idled.
159+
160+
In the web console, you will see your deployment as *Idled due to inactivity*
161+
and you can manually scale the deployment back up.
162+
163+
If network traffic does not restore a project's replica counts, then you may
164+
have to manually scale up the deployment.
165+
166+
[[account-pruning]]
167+
== Account Pruning
168+
If your {product-title} Starter account is inactive, meaning that you have had
169+
no running pods in your project for 3 days, you will receive a warning email
170+
that your account is to be deprovisioned. If you do not take corrective action
171+
and create pods within 5 days, your account is automatically deprovisioned. Once
172+
your account is deprovisioned, you can register again.
173+
endif::[]

0 commit comments

Comments
 (0)