apache / apache/solr-operator

Provide a tutorial for running solr-operator on microk8s / minikube.

Open
#153 3 comments 1 reaction 0 assignees View on GitHub
documentation
Dominant language
Go
Stars
283
Forks
148
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
Current Local Tutorial instructions don't work on microk8s or minikube.

**Describe the solution you'd like**
It would be great to provide instructions on how to run solr-operator on microk8s / minikube. Docker-edge on macOS has a bug that results in very high CPU usage even when idle.

**Additional context**
I followed the steps in the existing tutorial (plus some corrections) but this resulted in a non-functional Solr cluster.

The main issue seems to be that both microk8s and minikube use 10.x.x.x subnet for internal pod IPs (and each of them gets a different IP, unlike with Docker.app which seems to use 127.0.0.1 for all of them), and apparently the ingress configuration doesn't deal with it properly - in some cases I could use `minikube tunnel` to contact one of the nodes but it wouldn't be able to see any other node (or ZK).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the existing Local Tutorial and reproduce its steps on both microk8s and minikube, including the reported 10.x.x.x pod-network and ingress behavior. Done means documented, working instructions for running solr-operator and a functional Solr cluster on each environment, including any required corrections or use of minikube tunnel.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.