If you will ever need to change serviceSubnet CIDR range (e.g. Kubernetes pod-network-cidr and service-cidr can’t overlap with intranet network ranges) here is how to proceed:
Continue readingChange serviceSubnet in Kubernetes
Reply
Using c5d EC2 AWS instances in terraform-aws-eks module
c5d EC2 instances have internal NVMe storage. To use the advantage of NVMe internal disks in the terraform-aws-eks module as a Launch Template for the Autoscaler Groups the support was added in the following PRs:
- https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1213
- https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1404
In case you need a cost-effective AWS instance with high throughput and amount of IOPS this should be a good choice for EKS instances. A drawback could be instance has a fixed disk size of the NVMe disk.
More information about c5 instances with local NVMe storage can be found here:
- https://aws.amazon.com/blogs/aws/ec2-instance-update-c5-instances-with-local-nvme-storage-c5d/
- Comparsion between different disks and AWS instances: https://faun.pub/testing-the-waters-of-aws-ec2-c5d-instances-51fae49f33a3
List of supported AWS instances and other options in terraform-aws-eks module is defined by AWS CLI Reference in section option parameter ‘instance-type’ – https://docs.aws.amazon.com/cli/latest/reference/autoscaling/create-launch-configuration.html#options
Share CC2652RB (slae.sh) stick to zigbee2mqtt via ser2net
This is quick how-to share CC2652RB over network to zigbee2mqtt (Home Assistant) via ser2net. This tutorial is for RaspberryPi.
Continue readingPort 80 is being used by SYSTEM (PID 4)
If your application can’t start anymore on port 80 or you see HTTP Error 404. The requested resource is not found. it looks like http.sys placed reservation of port 80 and your application can’t start anymore.
In most cases this could happen after Windows Update or SCCM agent pushing updates and the agent won’t do the proper cleanup of reserved HTTP namespace.
Continue readingKubernetes pod-network-cidr and service-cidr can’t overlap with intranet network ranges
If you initialize Kubernetes cluster with kubeadm check with the network team if the ranges you provide to kubeadm with –pod-network-cidr and –service-cidr does not overlap with intranet network ranges. Otherwise, pods/services won’t operate well and you might see anomalies in your Kubernetes environment.
Continue readingDocker push fails with 504 Gateway Time-out
I was solving issues during large docker layers being uploaded to the SaaS Artifactory docker repository. Docker failed on large layers with the following error message:
received unexpected HTTP status: 504 Gateway Time-out