Check for shielded nodes and shutdown hours
Shielded nodes are not compatible with shutdown hours. If shutdown hours are enabled, make sure the Ocean controller is available when off-time ends.

• The controller must run on a node not managed by Ocean, because Ocean-managed nodes are scaled down during off-time.

• The controller is required for node registration. If it is unavailable, nodes remain unregistered.
  
  

Check if the cluster runs in a private network
Private GKE clusters require a NAT gateway so nodes can reach the internet. Without NAT access, nodes cannot pull images or connect to required services, causing node registration to fail.

To fix this, confirm that a NAT gateway is configured for the cluster’s subnet in Google Cloud.

Verify external NAT settings in the Ocean cluster configuration
Make sure the cluster has the correct external-nat and ONE_TO_ONE_NAT settings.

In the Flexera console:

1. Go to Ocean > Cloud clusters.

2. Select the cluster.

3. Choose Actions > Edit cluster.

4. Go to Review > JSON.

5. Confirm the network interface configuration matches the required format.
   
   

In the API, the compute section should include settings like:

{
  "compute": {
    "networkInterfaces": [
      {
        "network": "networkname",
        "accessConfigs": [
          {
            "name": "external-nat",
            "type": "ONE_TO_ONE_NAT"
          }
        ],
        "aliasIpRanges": [
          {
            "ipCidrRange": "/24",
            "subnetworkRangeName": "subnetworkRangeName"
          }
        ],
        "projectId": "projectId"
      }
    ]
  }
}

Restart or rescale the nodes
After correcting the NAT or shielded node configuration, restart or scale the virtual node group so new nodes can register successfully.