Ensuring the Ocean Controller is always scheduled

Title

The Ocean Controller is a critical component in AKS, EKS, and GKE clusters that use Flexera Ocean. Understanding how it is scheduled helps ensure it runs reliably and continues managing your cluster’s scaling and optimization.

Controller scheduling behavior

The Ocean Controller pod uses the system-node-critical priority class. This makes its scheduling nearly guaranteed because Kubernetes places top‑priority system workloads before other pods.

Ensuring continuous availability

You can make sure the controller is always running by setting a minimum capacity of at least one node in the cluster or in the virtual node group. This ensures that Kubernetes always has a node available for the controller pod to run on.

Was this helpful?

Support Hub

Product

Ocean

Visibility

Guest

URL Name

Ensuring-the-Ocean-Controller-is-always-scheduled

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Revenera Assistant

Controller scheduling behavior

Ensuring continuous availability

Related Articles

Please wait...

Case id: 00001065