You can use Scala Scripts for your scripting needs, and avoid You no longer have to drop down to Python or Bash for your scripting needs: Want to run it later, save it into some Scala Scripts and runįor a video overview of the project and it's motivation, check out this talk: Scala, open the Ammonite-REPL and run it, interactively! If you "projects", using the lightweight Ammonite runtime: if you want to run some
The goal of Ammonite is to liberate your Scala code from heavyweight You use Ammonite and enjoyed it, please chip in to support our developmentĪny amount will help us develop Ammonite into the best possible REPL and Helpful in using Ammonite to the fullest: If you use Ammonite, you will probably find the following book by the Author Setting up a "project" or waiting for SBT's slow startup times. This hooks can be in the form of container images or manifest files (systemd units).Run easily from the command line, without the overhead of
For instance you can install Nvidia drivers for using GPUs. Hooks allow for the execution of an action before the installation of Kubernetes on every node in a cluster. More information about running in an existing VPC is here. If creating a cluster from scratch, this field does not need to be specified at create time kops will create a VPC for you. On AWS, this is the id of the VPC the cluster is created in. Learn more about reserving compute resources here and here. The above will result in the flags -kube-reserved=cpu=1,memory=2Gi,ephemeral-storage=1Gi -kube-reserved-cgroup=/kube-reserved -kubelet-cgroups=/kube-reserved -runtime-cgroups=/kube-reserved -system-reserved=cpu=500m,memory=1Gi,ephemeral-storage=1Gi -system-reserved-cgroup=/system-reserved -enforce-node-allocatable=pods,system-reserved,kube-reserved being added to the kubelet. Spec : kubelet : kubeReserved : cpu : "1" memory : "2Gi" ephemeral-storage : "1Gi" kubeReservedCgroup : "/kube-reserved" kubeletCgroups : "/kube-reserved" runtimeCgroups : "/kube-reserved" systemReserved : cpu : "500m" memory : "1Gi" ephemeral-storage : "1Gi" systemReservedCgroup : "/system-reserved" enforceNodeAllocatable : "pods,system-reserved,kube-reserved" This will override the default limit value for memory of 170Mi and default request values for memory and cpu of 70Mi and 100m.
If you would like to continue autoscaling, update the kube-dns-autoscaler Deployment container command for -target=Deployment/kube-dns to be -target=Deployment/coredns.įor larger clusters you may need to set custom resource requests and limits. The kube-dns Service itself should be left in place, as this retains the ClusterIP and eliminates the possibility of DNS outages in your cluster. Note: If you are upgrading to CoreDNS, kube-dns will be left in place and must be removed manually (you can scale the kube-dns and kube-dns-autoscaler deployments in the kube-system namespace to 0 as a starting point). Spec : kubeDNS : provider : CoreDNS coreDNSImage : /mirrors/coredns:1.3.1 externalCoreFile : | :53 Of Kubernetes this will disable the passing of the -basic-auth-file flag when: Support for basic authentication was removed in Kubernetes 1.19.
See also Kubernetes certificates Disable Basic Auth ¶ The refresh ca.crt logic can also be achieved by writing a kops hook. If a customized client-ca file is used, when kOps cert rotation happens, the user is responsible for updating the ca.crt in the customized client-ca file. Kops has a CA rotation feature, which refreshes the Kubernetes certificate files, including the ca.crt. One way to append the ca.crt to the end of the customized client-ca file is to write an kop-hook to do the append logic. In the case that the user would use a customized client-ca file, it is common that the kubernetes CA ( /srv/kubernetes/ca/crt) need to be appended to the end of the client-ca file. To prepare the customized client-ca file on master nodes, the user can either use the fileAssets feature to push an client-ca file, or embed the customized client-ca file in the master AMI. In that case, the user can use this flag to specify the client-ca file to use.
There are certain cases that the user may want to use a customized client CA file other than the default one generated for Kubernetes. Spec : kubeAPIServer : clientCAFile : /srv/kubernetes/client-ca.crt Moving from a Single Master to Multiple HA Masters Service Account Issuer Discovery and AWS IAM Roles for Service Accounts (IRSA) Optional step: add root certificates to instancegroups root ca bundle
Setting kubelet configurations together with the Amazon VPC backend