The correct way to determine k8s-user-startup- script

This is similar to the following question: Recommended way to constantly change kube-env variables

I played with the ability to define k8s-user-startup-script for GKE instances (I want to install additional software for each node).

Adding k8s-user-startup-script to the User Metadata instance group template works, but it is overwritten gcloud container clusters upgrade, which creates a new Template instance without "inheriting" the additional k8s-user-startup-script Metadata from the current template.

I also tried adding k8s-user-startup-script to the project metadata (I thought it would be inherited by all instances of my project, as described here ), but this is not taken into account.

What is the correct way to define a k8s-user-startup-script that saves cluster updates? Or, more generally, what is the desired way to configure GKE nodes?

+4
source share
1 answer

The Google Container Engine does not support custom startup scripts for nodes.

kube-env, DaemonSet . DaemonSet, , , script, , node. DaemonSet , , ( ) , API Kubernetes, .

+5

All Articles