Sign in

Serkan Capkan

As a “Managed Kubernetes” offering, AWS EKS comes with some essential core services, like CoreDNS. (kube-proxy etc.)

CoreDNS is an open source DNS service with Kubernetes plugin for service discovery and by default it’s a DNS server for most of the Kubernetes distribution. Service discovery is actually the main motivation behind hosting a DNS server inside the Kubernetes cluster, otherwise all DNS queries would go to external DNS server. Better to explain with a drawing;


As someone working from different locations and home for long years, I have some tips for people will work remotely upcoming weeks.

Don’t forget that, although working from home sounds super cool, office environment gives you social interaction, some healthy rhythms, helps you leave the work behind. Not following some simple tips can cause not enjoying your days, not being productive and feeling working 24 hours.

Here are my tips;

  • It’s not vacation: I’m not your manager, not trying to motivate you. But if you would like to spend your time healthy at home, first realise that, it’s not vacation.

On this post I’ll summarize how to expose web applications on EKS (or self managed Kubernets) in a fully automated AWS infrastructure environment, mentioning challenges together with solutions.

Let’s start with the default option we know from Kubernetes 101. In order to expose an application at Kubernetes, you should create a Service, with type LoadBalancer. This method is correct and provided directly by Kubernetes*.

*https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types

apiVersion: v1
kind: Service
metadata:
name: service-public-app1
spec:
type: LoadBalancer # <- Creates AWS Classic Load Balancer
selector:
app: my-public-service
ports:
- protocol: TCP
port: 80

This declaration will create an AWS Classic LoadBalancer and…


If you’re configuring a web application on AWS, whether it’s a serverless, Kubernetes or EC2 based solution, it’s quite common to have CloudFront as CDN, AWS WAF as Web Application Firewall and AWS Elastic Load Balancer in front of your web service.

Purpose of each components can be listed as;

AWS Web Application Firewall:

  • IP based restriction to protect some pages from public access.
  • URL based restriction to protect some URIs from public access.
  • Protect applications against common web exploits.

CloudFront

  • Caching static contents
  • Catching error pages and showing custom error pages
  • Serving static content directly from S3 bucket

S3


One of our first challenge is to bring Ada from Aalsmeer to Amsterdam Marina. I was preparing for some time and here is some findings.

Some links about standing mast route and my planned route at the bottom

Main challenge with this passage is bridge opening hours, on this page, all informations like opening hours, phone numbers, VHF channels etc. can be found.

https://vaarweginformatie.nl/fdd/main/infra/vin?tabIndex=1

It’s very important to check it in front as from time to time waternet or NS do maintenance on the bridges and locks and they can be closed for all night or even for days.

We’ll…

Serkan Capkan

Solutions Architect | Cloud | AWS | Kubernetes

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store