kube | responsive Hugo theme for developers and designers | Static Site Generator library

I originally posted this question as an issue on the GitHub project for the AWS Load Balancer Controller here: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2069.

I'm seeing some odd behavior that I can't trace or explain when trying to get the loadBalacnerDnsName from an ALB created by the controller. I'm using v2.2.0 of the AWS Load Balancer Controller in a CDK project. The ingress that I deploy triggers the provisioning of an ALB, and that ALB can connect to my K8s workloads running in EKS.

Here's my problem: I'm trying to automate the creation of a Route53 A Record that points to the loadBalancerDnsName of the load balancer, but the loadBalancerDnsName that I get in my CDK script is not the same as the loadBalancerDnsName that shows up in the AWS console once my stack has finished deploying. The value in the console is correct and I can get a response from that URL. My CDK script outputs the value of the DnsName as a CfnOutput value, but that URL does not point to anything.

In CDK, I have tried to use KubernetesObjectValue to get the DNS name from the load balancer. This isn't working (see this related issue: https://github.com/aws/aws-cdk/issues/14933), so I'm trying to lookup the Load Balancer with CDK's .fromLookup and using a tag that I added through my ingress annotation:

I installed a Kubernetes cluster of three nodes, the control node looked ok, when I tried to join the other two nodes the status for both of is: Not Ready

On control node:

I am trying to install my rancher(RKE) kubernetes cluster bitnami/mongodb-shared . But I couldn't create a valid PV for this helm chart.

The error that I am getting: no persistent volumes available for this claim and no storage class is set

This is the helm chart documentation section about PersistenceVolume: https://github.com/bitnami/charts/tree/master/bitnami/mongodb-sharded/#persistence

This is the StorageClass and PersistentVolume yamls that I created for this helm chart PVCs':

Say I have multiple namespaces on a kube cluster and each namespace has a RMQ container, and these RMQ containers are spread throughout a few nodes, is there a way to deploy one metricbeat pod (preferably as a daemonset) per node to monitor these RMQ containers? What's the best practice regarding using Metricbeat for monitoring, do you need one metricbeat per container? Thanks.

I want to be able to use kubectl commands on my master ec2 instance from my local machine without ssh. I tried copying .kube into my local but the problem is that my kubeconfig is using the private network and so when i try to run kubectl from my local I can not connect.

Here is what I tried:

I have the minikube environment as the following: -

• Host OS: CentOS Linux release 7.7.1908 (Core)
• Docker: Docker Engine - Community 20.10.7
• minikube: minikube version: v1.20.0

I would like to add some additional host mapping (5+ IP and name) to the /etc/hosts inside the minikube container. Then I use the minikube ssh to enter to the shell and try to echo "172.17.x.x my.some.host" >> /etc/hosts. There is an error as -bash: /etc/hosts: Permission denied since the user who login to this shell is a docker, not a root.

I also found that at the host machine there is a docker container named minikube running, by using the docker container ls. Even I can go to this container with root by using docker exec -it -u root minikube /bin/bash. I understand that it is a kind of tweak and may be a bad practice. Especially it is too much tasks.

Regarding to the docker and docker-compose which provides the --add-host and extra_hosts respectively to add hostname mappings, Does the minikube provide it? Is there any good practice to achieve this within the minikube and/or system administrator point-of-view good practice?

After echo 172.17.x.x my.some.host > ~/.minikube/files/etc/hosts and start the minikube, there are some error as the following: -

I'm trying to deploy kubeflow on and OVH managed k8 cluster.

After the initial setup of the k8 cluster, I ran the following commands to install kubeflow, as suggested here: