orientechnologies / orientechnologies/orientdb-helm

Config orientdb service as LoadBalancer

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
6
Forks
4
PR merge metrics
No merged PRs in 30d

Description

I wished to configure the orientdb service as a LoadBalancer with session affinity.

I made a change in the statefulset.yaml (adding type: LoadBalancer) but it makes an error (orientdb service exists already).

In fact the yaml files of the chart must not be changed.

After the helm install instruction, I have added :

kubectl delete service orientdb
kubectl apply -f orientdb-helm-values-patch.yaml 

The file orientdb-helm-values-patch.yaml is :

apiVersion: v1
kind: Service
metadata:
  namespace: default
  name: orientdb
  labels:
    app: orientdb
spec:
  ports:
  - port: 2424
    name: binary
  - port: 2480
    name: http
  - port: 2434
    name: hazelcast
  type: LoadBalancer  
  sessionAffinity: ClientIP
  selector:
    app: orientdb

PS : this issue because it costed me several days to find the issue and fix it !

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the chart's statefulset.yaml and the orientdb-helm-values-patch.yaml example, then trace how the orientdb Service is created during helm install. Check whether service type and sessionAffinity can be supplied through chart values without deleting the existing Service; done means a clean install produces a LoadBalancer Service with ClientIP affinity and the existing ports.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.