wireapp / wireapp/wire-server-deploy

Getting the unreachable Host for the kubenode01

Open
#242 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
113
Forks
44
PR merge metrics
No merged PRs in 30d

Description

My question: I followed the Step in the Documentation which is provided and I want to install the server offline using Docker Container and kubernetes but when I run this step poetry run ansible-playbook -i hosts.ini kubernetes.yml -vv I get the Error for the same.

Context:

Please provide sufficent context about your problem:

How did you install wire-server?

On kubernetes With docker-compose

How many servers are involved => 1 Server that is the Docker installed in my system along with the kubernete
What is installed on which servers? => Docker and kubernetes

E.g Server A has component X and server B has component Y

Provide details about networking

We don't need to know any specific IP address, but it helps if you provide information whether an IP is ipv4 or ipv6, whether is is publicly reachable from the global internet or not, and if you installed any component of wire-server, which network interfaces are processes listening on?

How did you configure wire-server?

Note: only the configuration from helm charts in wire-server-deploy is what we support, like these defaults applied here in the case of brig. If you have used other configuration files, please post them (or the relevant parts of them).
Did you use the helm charts from wire-server-deploy?
Did you use and adapt configuration files from wire-server? If so, which ones?
Are there any overrides?

Screenshot 2020-04-22 at 7 51 19 PM

Contributor guide

Open the contributing guide

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 with hosts.ini and kubernetes.yml, then rerun poetry run ansible-playbook -i hosts.ini kubernetes.yml -vv to capture the unreachable-host error for kubenode01. Done means the playbook can reach the single Docker and Kubernetes server, or the issue documents the missing networking or host configuration needed to do so.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, docker, helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.