<p>I'm create GKE clusters for end-to-end tests programmatically with</p>

<pre><code>gcloud container clusters create mereet-e2e-$CI_COMMIT_SHORT_SHA-$CI_PIPELINE_IID --machine-type=n1-standard-1 --no-enable-stackdriver-kubernetes --no-enable-autoupgrade --preemptible --enable-kubernetes-alpha --quiet
</code></pre>

<p>Afaik feature flags are enabled with <code>kubeadm init</code> which is run by GKE. I searched carefully through options of <code>gcloud</code>, <code>gcloud container</code>, <code>gcloud container clusters</code> and <code>gcloud container clusters create</code> as well as their <code>gcloud alpha</code> and <code>gcloud beta</code> equivalents with no clue how to control feature gates.</p>

<p>I would like to activate the feature gate <code>StartupProbe</code>.</p>

<p>I tried beta and alpha clusters in the hope that my feature gate is already active in these versions. It's not a problem that the feature will be only available in beta or alpha.</p>

Kalle Richter
<p>Accroding to the docs, StartupProbe is a 1.16 alpha feature, while on GKE you can create clusters up to 1.14.</p>

<p><a href="https://i.stack.imgur.com/qgik2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/qgik2.png" alt="enter image description here"></a></p>

<p>So, it won't even be documented in GCP docs. Besides, note that you don't have access to k8s master on GKE. Only to some features.</p>

<p>With <code>kubeadm</code> you can do whatever you want.</p>
