From 3a575706e6231b640ef9a1181ca50711052f025f Mon Sep 17 00:00:00 2001
From: Rachel Hooley <167069628+RachelHooley@users.noreply.github.com>
Date: Wed, 18 Dec 2024 15:58:15 +0200
Subject: [PATCH] Update README.md doc-2156 (#5189)
---
src/docs/faqs/README.md | 24 +++++++++++++++++++++---
1 file changed, 21 insertions(+), 3 deletions(-)
diff --git a/src/docs/faqs/README.md b/src/docs/faqs/README.md
index e9df9aedc..5c24dd6fa 100644
--- a/src/docs/faqs/README.md
+++ b/src/docs/faqs/README.md
@@ -839,14 +839,18 @@ Then [create or update](https://github.com/spotinst/spotinst-sdk-python/blob/v2/
- AKS, EKS, GKE: Should I get frequent SelfSubjectAccessReview requests after upgrading to Ocean Controller Version 2?
+ GKE: Why can't I spin new spot instances (InstanceTaxonomies)?
+You can get this message if the instance type is not compatible with the boot disk type:
-After you upgrade to Ocean Controller Version 2, you may get many SIEM alerts due to SelfSubjectAccessReview requests to your API server. This is expected behavior.
+```ERROR, Can't Spin Instance: Name: sin-xxxx. Code: Error, Message: [pd-standard] features and [instance_type: VIRTUAL_MACHINE family: COMPUTE_OPTIMIZED generation: GEN_3 cpu_vendor: INTEL architecture: X86_64 ] InstanceTaxonomies are not compatible for creating instance.```
+
+[Compare the machine family](https://cloud.google.com/compute/docs/machine-resource#machine_type_comparison) and PD-standard disk type to decide which is appropriate for your workload.
+
+Contact support to decide on the selected instance type for launching and to remove the problematic instance type or family from the allowlist.
-With the Version 2 Ocean Controller, Spot gets reports for any custom resource you gave it access to through the controller cluster role. For example, an Argo Rollouts custom resource or a VerticalPodAutoscaler for rightsizing. These require Spot to list the custom resources in the cluster and make sure there's read access. This happens when the controller starts up and on a regular basis when it's running.
@@ -874,6 +878,20 @@ This will let you manually increase the target of the cluster and the nodes will
+
+
+
+ AKS, EKS, GKE: Should I get frequent SelfSubjectAccessReview requests after upgrading to Ocean Controller Version 2?
+
+
+
+
+After you upgrade to Ocean Controller Version 2, you may get many SIEM alerts due to SelfSubjectAccessReview requests to your API server. This is expected behavior.
+
+With the Version 2 Ocean Controller, Spot gets reports for any custom resource you gave it access to through the controller cluster role. For example, an Argo Rollouts custom resource or a VerticalPodAutoscaler for rightsizing. These require Spot to list the custom resources in the cluster and make sure there's read access. This happens when the controller starts up and on a regular basis when it's running.
+
+
+