In July 2026, GreenNode introduces two updates aimed at the same goal: simplifying infrastructure operations and reducing repetitive manual work. GreenNode CLI takes the full Kubernetes cluster lifecycle out of the Portal and into the terminal, while Operations Manager brings automated VM scheduling to vServer at scale.
VKS: GreenNode CLI brings Kubernetes management to the terminal
Users can now manage the full lifecycle of Clusters and Node Groups directly from the terminal using the grn command, with no need to work through the Portal. The tool is built for fast operations, script-based automation, and direct integration into CI/CD pipelines, serving teams that want infrastructure management to live inside their existing pipeline rather than a manual, web-based workflow.
vServer: Operations Manager brings automated VM scheduling
Instead of performing actions manually one at a time, Operations Manager lets you schedule START / STOP / REBOOT operations on VMs at fixed daily time windows, applied to one or multiple VMs at once, within an optional validity period.
A standout capability is tag-based VM selection: any VM carrying the matching tag automatically falls within the task's execution scope at runtime. A newly tagged VM is picked up immediately without needing to update the task, meaningfully cutting maintenance overhead as infrastructure changes frequently.
Full task lifecycle management
Create, update, duplicate, disable, delete, and trigger a task manually and immediately when handling an emergency or verifying a configuration, without waiting for the scheduled time. Execution history shows detail down to each individual VM, success/failure status and specific error messages, making it fast to identify the root cause when something goes wrong.
Safe operations, lower configuration risk
Before every execution, the system automatically reconciles the VM list against vServer: deleted VMs are automatically excluded from the task, and a duplicate-execution safeguard ensures each schedule runs exactly once. Activation is a one-time step, the system automatically provisions a dedicated Service Account with least-privilege access for each user.
Operations Manager is now available in HCM-03 and HAN-01. Each account is provisioned with a default limit of 20 tasks.
Customers can log in to the Portal to try the new features, or contact the GreenNode team for consultation and deployment support.
AgentBase: New security and integration capabilities for AI agents
GreenNode AgentBase adds two features aimed at tightening access control and expanding integration options for AI agents.
Security Runtime: controlling who can access a Runtime
At Runtime creation, users can configure IP Access Control (allowed source CIDR ranges) and Inbound Identity (authenticating incoming requests via IAM Permissions, JWT, or no authorization) — giving tight control over which clients can call into a Runtime and how requests get authenticated.
MCP Connectors: connect agents to external services in minutes
Agents can connect directly to external services such as GitHub, Slack, and Microsoft 365 (M365 VNG bundle) through a ready-made connector catalog, with no need to build an MCP server or hand-roll an OAuth flow.
Technical documentation
- Manage VKS with the GreenNode CLI
- vServer Operations Manager
- Announcements and Updates
- MCP Connectors
- AgentBase Runtime
Frequently Asked Questions
How is GreenNode CLI (grn) different from working through the Portal?
GreenNode CLI manages the full lifecycle of Clusters and Node Groups through direct commands from the terminal, instead of clicking through a web interface. The key difference is the ability to script actions and integrate them into CI/CD, useful when the same operation needs to run repeatedly across multiple environments or as part of an automated deployment process.
Can Operations Manager be used on production VMs?
Yes. Operations Manager schedules START/STOP/REBOOT actions by tag, with no restriction on workload type. That said, since STOP/REBOOT actions directly affect running VMs, the time window and tag scope should be carefully reviewed before applying them to a production environment.
If a new VM is created with a tag already used in a task, will it automatically be included in the schedule?
Yes. The system determines a task's VM scope by tag at execution time, not at task-creation time. A newly tagged VM is therefore picked up starting from the next run, with no need to update the task configuration.
What happens if a VM included in a task is deleted?
Before each execution, the system automatically reconciles the VM list against vServer. A deleted VM is automatically excluded from the task's execution scope, without triggering errors or false alerts.
What is the maximum number of Operations Manager tasks per account?
The default limit is 20 tasks per account. The feature is currently available in two regions: HCM-03 and HAN-01.
Does using Operations Manager require setting up separate IAM permissions?
No manual setup is needed. On first activation, the system automatically provisions a dedicated Service Account for each user with the minimum permissions required.
How does Security Runtime protect a Runtime from unwanted access?
Through two layers of control: IP Access Control restricts access by source CIDR range, and Inbound Identity governs how incoming requests are authenticated (IAM Permissions, JWT, or left open if no authorization is needed). Both are configured at Runtime creation and don't need to be set up again afterward.
Do I need to build my own MCP server to use MCP Connectors?
No. MCP Connectors provides a ready-made catalog for services like GitHub, Slack, and Microsoft 365 (M365 VNG bundle) — agents connect directly within minutes, with no need to build an MCP server or hand-roll an OAuth flow.
