kops | Kubernetes Operations - Production Grade k8s | Continuous Deployment library

Basically, I had installed Prometheues-Grafana from the kube-prometheus-stack using the provided helm chart repo prometheus-community

I'm having to build a demo Kubernetes cluster in AWS using Kubeadm.

Unfortunately, for several reasons, Kops, and EKS are out of the question in my current environment.

How do I deal with things such as auto-scaling and auto joining worker nodes back to the master if they get terminated for any reason? This is my main concern.

I've done this with Kops in the past and it's relatively straightforward, but I'm not sure how to manage using Kubeadm.

Does anybody know when creating InstanceGroup using kops, why we set both machineType and mixedInstancesPolicy? Does machineType means kops will pick machineType by default but if no instance with machineType available it will pick one of the types from mixedInstancesPolicy?

The spec: https://kops.sigs.k8s.io/instance_groups/ shows: "A Mixed Instances Policy utilizing EC2 Spot and the capacity-optimized allocation strategy allows an EC2 Autoscaling Group to select the instance types with the highest capacity. This reduces the chance of a spot interruption on your instance group."

the spec does not show what machineType is and what is the difference of machineType and mixedInstancesPolicy.

I've recently started using KOPS as a tool to provision Kubernetes clusters and from what I've seen so far, it stores it's CA key and certificates in its S3 bucket, which is fine.

But out curiosity, would it be possible to store these in Hashicorp Vault instead, as opposed to s3?

I have created a k8s cluster with kops (1.21.4) on AWS and as per the docs on autoscaler. I have done the required changes to my cluster but when the cluster starts, the cluster-autoscaler pod is unable to schedule on any node. When I describe the pod, I see the following:

This is really annoying me and I can't seem to find any answers on the internet.

I created a cluster using kops on AWS yesterday and everything worked fine. But for some reason (and this is like the 5th time it happens), I come back 1 or 2 days after and simply cannot access the cluster. All the other times my solution was to delete everything manually and create the cluster again.

Here's my kubectl client version

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:41:28Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}

Here's what I tried:

1. kubectl get nodes/pods/services/etc -v 7

I've used the Bitnami Helm chart to install SCDF into a k8s cluster generated by kOps in AWS.

I'm trying to add my development SCDF stream apps into the installation using a file URI and cannot figure-out where or how the shared Skipper & Server mount point is. exec'ing into either instance there is no /home/cnb and I'm not seeing anything common via mount. The best I can tell the Bitnami installation is using the MariaDB instance for shared "storage".

Is there a recommended way of installing local/dev Stream apps into the cluster?

I want to create cluster on gcp using kops.

For this, first I created gcs bucket. Then exported value for KOPS_STATE_STORE as

I am trying to implement some of the CIS security benchmark advices to kubernetes version 1.21.4 via kOps(1.21.0) for a self hosted Kubernetes on aws.

However when i try protectKernelDefaults:true in kubelet config and EventRateLimit adminssion plugin kube api server config, the k8s cluster fails to come up. I am trying bring up a new cluster with these settings not trying to update any existing ones.

kops cluster yaml that i am trying to use is