How to set up Traefik running as ingress controller in Kubernet to forward requests to a Kubernetes service backend that uses the HTTPS protocol and self-signed certificate.
References links
How to set up Traefik running as ingress controller in Kubernet to forward requests to a Kubernetes service backend that uses the HTTPS protocol and self-signed certificate.
References links
When you install EKS for the first time, you receive the following message in the AWS Console UI.
Your current user or role does not have access to Kubernetes objects on this EKS cluster. This may be due to the current user or role not having Kubernetes RBAC permissions to describe cluster resources or not having an entry in the cluster’s auth config map.
This happen because your AWS user account doesn't have access to the Kubernetes control plane.
Kubernetes by default doesn't provide this feature but you can use Another Autoscaler controller for that.
We are using this tool in my company to save some money on the Kubernetes clusters with GPU instances (P2 and G4DN); Developers using these types of instances generally use them during working hours, so we can terminate pods after working hours and our Cluster Autoscaler will scale-down instances that are idle.
Another Autoscaler page: https://github.com/dignajar/another-autoscaler
Time for GPU and Kubernetes, the idea is to provide an instance group with Kubernetes' nodes with GPU, also to save some money we can start the autoscaling group from 0 instances.
Assuming you have deployed AWS Load Balancer Controller, the following steps are how to configure one ALB to expose all your services, also services cross namespaces.
Default configuration for the ALB "dev" with the following features:
The idea is to wait inside an init-container
until the health check is successful. The health check, in this case, is the HTTP response code equal to 200.
init-container
will continue after the service returns 200
.init-container
doesn't complete, the container will not be executed.initContainers:
- name: wait-for-webserver
image: curlimages/curl:latest
command: ["/bin/sh","-c"]
args: ["while [ $(curl -sw '%{http_code}' http://webserver.svc.cluster.local -o /dev/null) -ne 200 ]; do sleep 5; echo 'Waiting for the webserver...'; done"]