Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

Operator stuck in Wait for Database phase on non-openshift distros #38

Open
garyedwards opened this issue May 21, 2020 · 1 comment
Open

Comments

@garyedwards
Copy link

Description

Operator does not detect that the database is running on GKE and k3s distros of k8s.

Expected Behavior

After the postgres pod reaches a running state the gitea pod to be created.

Actual Behavior

The operator remains in Phase: Wait for Database.

Environment

  • Operating system: Fedora 32.20200512.0
  • Kubernetes version: k3s: v1.17.2+k3s1 containerd:1.3.3-k3s1
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:30:10Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2+k3s1", GitCommit:"cdab19b09a84389ffbf57bebd33871c60b1d6b28", GitTreeState:"clean", BuildDate:"2020-01-27T18:09:26Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
  • Project Version/Tag: 0.0.5

Steps to reproduce

  • Install the operator and example cr as per the Makefile substituting oc commands for kubectl including the example cr.
  • Check the running pods (postgres should be up and running fine)
  • Check operator logs (stuck in Phase: Wait for Database)

I am not sure if this is a openshift vs non-openshift distros. It would be great if the operator could be made more distro agnostic.

@btsken
Copy link

btsken commented Aug 5, 2020

I got the same issue

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants