In the previous post – Neo4j: graph database – run with Docker and Cypher QL examples – we’ve run the Neo4j database with в Docker. The next task is to run it in the Kubernetes cluster. Will use the Neo4j Community Edition, which will be running as a single-node instance as cluster ability for the… Read More: Neo4j: running in Kubernetes0 (0) »
For the persistent data Kubernetes provides two main types of objects – the PersistentVolume and PersistentVolumeClaim. PersistentVolume – is a storage device and a filesystem volume on it, for example, it could be AWS EBS, which is attached to an AWS EC2, and from the cluster’s perspective of view, a PersistentVolume is a similar resource… Read More: Kubernetes: PersistentVolume and PersistentVolumeClaim – an overview with examples0 (0) »
In contrast to the RDMS (Relational Database Management System), where data objects are the main part, in a Graph Database, the relations between such data objects are playing the main role and are represented as dedicated objects which gives better performance especially when you have a lot of small data pieces tied to each other.… Read More: Neo4j: graph database – run with Docker and Cypher QL… »
We have a Kubernetes Cron Job which failed on its last run. Let’s look for the root cause and then will see how to restart such a failed job. List current jobs: [simterm] $ kk -n eks-prod-1-bttrm-apps-ns get cronjobs NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE bttrm-apps-backend-reccuring-payment-cron 0 10 * * * False 1 22m… Read More: Kubernetes: manually restart a Cron Job0 (0) »
Currently, to collect metrics from the AWS CloudWatch we are using AWS’s own cloudwatch-exporter, see the Prometheus: CloudWatch exporter — сбор метрик из AWS и графики в Grafana post (in Rus), but it has a few gaps: it’s written in Java, so uses CPU/memory of the monitoring host doesn’t scrapes AWS tags from resources uses… Read More: Prometheus: yet-another-cloudwatch-exporter – collecting AWS CloudWatch metrics0 (0) »
For network communications, Kubernetes presents four Service types – ClusterIP (the default one), NodePort, LoadBalancer, and ExternalName, plus the Ingress resources. In this post, we will take a short overview of all of them, and will check how they are working. The documentation is available here – Publishing Services (ServiceTypes). I’m using AWS Elastic Kubernetes… Read More: Kubernetes: ClusterIP vs NodePort vs LoadBalancer, Services, and Ingress –… »
We have a Redis service running behind a Service with the ClusterIP type. This Redis must accessible by pods from the same namespace (a Gorush service). The problem is that those pod can’t connect to the Redis service using its gorush-server-redis-svc:6379 name and reporting “Can’t connect redis server: connection refused“: [simterm] $ kk -n gorush-test… Read More: Kubernetes: 503 no endpoints available for service – causes and… »
I have a CloudFormation stack with VPC Peerings, in that case, it’s a peering between VPC of a new Elastic Kubernetes Service cluster and VPC of the Prometheus monitoring stack. The EKS cluster’s stack and its whole automation creation were described in the AWS Elastic Kubernetes Service: a cluster creation automation, part 1 – CloudFormation… Read More: AWS: CloudFormation – using Conditions, Fn::Equals, and Fn::If – an… »
During a Docker image build – it stops asking to configure the tzdata. Dockerfile at this moment is the next: FROM ubuntu:18.04 RUN apt update && apt install -y python-pip python-dev ssh python-boto3 RUN pip install ansible==2.4.3.0 Let’s reproduce – run the build: [simterm] admin@jenkins-production:~$ docker build -t proj/proj-ansible:1.1 . Sending build context to Docker… Read More: Docker: configure tzdata and timezone during build0 (0) »
So, as a follow-up to the Helm: Kubernetes package manager – an overview, getting started post – let’s discuss about sensitive data in our Helm charts. What I want is to store a chart files in a repository, but even if such a repo will be a private Github repo – I still don’t want… Read More: Helm: helm-secrets – sensitive data encryption with AWS KMS and… »