Operations on Environment
Last updated
Last updated
Odin provides users with the capabilities where users can use CLI commands to customise the default suspension and resume schedule for kube based environments. Currently the following operations are supported:
The above command will not downscale any components of the environment in the next auto suspension schedule and defer this to next to next suspension schedule. E.g: If the auto-suspension is scheduled for 2024-01-01 20:00PM, and you execute the above command at 2024-01-01 19:00PM, your environment will not be suspended at 20:00PM. However, next day your environment will again be suspended at 2024-01-02 20:00PM.
The above command will downscale all the components of the environment with an ETA of <2minutes for executing the request. However, this operation is applicable only for containerised components. The environment remains suspended until user manually resumes the environment.
The above command will upscale all the downscale component of the particular environment. This operation can be used to resume any auto suspended or manually suspended environment.
Q: Can I downscale my EC2 based components as part of environment suspension?
A: No, only containerised components are available for downscaling.
Q: I tried suspending my environment manually, but it is still running. Why?
A: Each suspension request takes upto 2-mins to get processed. Please check the status of environment after a while.
Q: Can I skip my environment from suspension for a long time duration?
A: No, if you user skip-suspend operation, this will skip the suspension of your environment from next auto-suspension schedule, not beyond that.
Q: Can anyone suspend my environment?
A: Currently, due to lack of RBAC, anyone can suspend any environment.