I am using AKS and recently upgraded to AKS 1.24.6.
How to determine what version of kube state metrics supports what AKS version?
I am looking at this https://github.com/kubernetes/kube-state-metrics
I am unable to understand the matrix given between Kube state metrics and Client-Go version.
According to the matrix, you can either use v2.5.0 or v2.6.0.
Related
We are currently running "composer-2.0.7-airflow-2.2.3" on GKE v1.21.x.
Looking to upgrade to GKE v1.22.x there are warnings of deprecated API's no longer available in v1.22 being used.
Can you advise if Cloud Composer will fix / or has fixed the use of deprecated API's in any later versions ?
This message seems to be occurring due to the deprecated APIs in Kubernetes where Beta APIs have since graduated from Beta (v1beta1) to GA (v1) as given in this documentation.
According to this official documentation, it should not affect Autopilot Clusters in GKE as whenever an autopilot Cluster is created,auto-upgrade is enabled on the cluster and the node pools by default which results in less distruption in the services.Since Autopilot clusters are enabled with auto-upgrade, they always run in the same version of GKE as the cluster itself.
I've read kubernetes and minikube docs and it's not explicit if minikube implementation supports automatically log rotation (deleting the pod logs periodically) in order to prevent the memory to be overloaded by the logs.
I'm not talking about the various centralized logging stacks used to collect, persist and analyze logs, but the standard pod log management of minikube.
In kubernetes official documentation is specified:
An important consideration in node-level logging is implementing log rotation, so that logs don’t consume all available storage on the node. Kubernetes currently is not responsible for rotating logs, but rather a deployment tool should set up a solution to address that. For example, in Kubernetes clusters, deployed by the kube-up.sh script, there is a logrotate tool configured to run each hour. You can also set up a container runtime to rotate application’s logs automatically, for example by using Docker’s log-opt. In the kube-up.sh script, the latter approach is used for COS image on GCP, and the former approach is used in any other environment. In both cases, by default rotation is configured to take place when log file exceeds 10MB.
Of course if we're not in GCP and we don't use kube-up.sh to start the cluster (or we don't use Docker as container tool) but we spin up our Cluster with Minikube what happens?
As per the implementation
Minikube now uses systemd which has built in log rotation
Refer this issue
I am planning to start my project but a bit confuse between choosing Amazon ECS and Kubernetes perhaps I am really a beginner with Micro-services architecture.
I would really appreciate if someone can show some path for deploying my docker container on a fast easier to handle platform.
Thanks
Here a list of differences from the top of my head:
AWS ECS / Kubernetes:
Proprietary AWS implementation / Open source solution
Runs on AWS / Supported by most cloud providers and on premise
Task Definitions / PODs have different features
Runs on your EC2 machines or allows for serverless with Fargate (in beta) / Runs on any cluster of (physical/virtual/cloud) machines running the kubernetes controller.
Support for AWS VPCs / Support for multiple networking models
I would also argue that kubernetes has a slightly steeper learning curve but ultimately provides more freedom and is probably a safer bet for the future given the wide adoption.
Features supported in both systems:
Horizontal application scalability
Cluster Scalability
Load Balancing
Rolling upgrades
Logging (with additional logging systems)
Container Health Checks
APIs
Amazon has bowed to customer pressure and currently has a managed kubernetes support in beta (EKS).
*edit: EKS is released now - but with an upcharge for the cluster controller nodes, as compared to google GKE for example.
Here is one article about the topic.
istio An open platform to connect, manage, and secure micro-services looks very interesting, but supports only Kubernetes. I couldn't find a roadmap or mention of future support for other container management platforms, specifically Docker Swarm
The project's github site does state the following explicitly:
Istio currently only supports the Kubernetes platform, although we
plan support for additional platforms such as Cloud Foundry, and Mesos
in the near future.
I don't know about the plans for Docker Swarm however I believe it probably would figure in the plans.
The roadmap at https://istio.io/docs/reference/release-roadmap.html shows that VM support is planned for 0.2
You can see that work is happening in the Cloud Foundry world when you see issues such as this.
The docker team indicated recently they are very interested in looking at istio and docker swarm integration so stay tuned this may happen in the next few quarters before you know it :)
Does any one of know which version of calico works with Docker in Swarm Mode?
Per https://docs.docker.com/engine/extend/plugins_network/ :
Docker 1.12 adds support for cluster management and orchestration called swarm mode. Docker Engine running in swarm mode currently only supports the built-in overlay driver for networking. Therefore existing networking plugins will not work in swarm mode.
I have heard this may be fixed for the upcoming 1.13.1 - so this could change very soon.
In order to work in swarm-mode, the calico plugin must be implemented as a managed plugin.
Calico project should also be swarm-mode compatible and support it.
Some more discussion here https://github.com/projectcalico/calicoctl/issues/1133 on expecting version Calico v2.3.0, Calico v2.2.0, but there is no official confirmation on that.
Though expectation was with Docker 1.13, no official confirmation or documentation on this.
Hope that help