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

Controller reflector failures when deployed with helm #66

Closed
wallrj opened this issue Oct 30, 2017 · 1 comment
Closed

Controller reflector failures when deployed with helm #66

wallrj opened this issue Oct 30, 2017 · 1 comment
Labels

Comments

@wallrj
Copy link
Member

wallrj commented Oct 30, 2017

The helm chart quotes the controller namespace.

/kind bug

What happened:

  • deployed navigator using e2e test script
  • controller did not react to any of the navigator API resources that I added.
  • It logged attempts to connect to e.g. https://10.0.0.1:443/apis/navigator.jetstack.io/v1alpha1/namespaces/%22default%22/elasticsearchclusters?resourceVersion=0

What you expected to happen:

It should create service and statefulset resources for the Cassandra or ElasticSearch cluster.

How to reproduce it (as minimally and precisely as possible):

Run e2e tests and watch for services created in the test namespace.

@wallrj
Copy link
Member Author

wallrj commented Oct 31, 2017

This is probably fixed by: #70

@wallrj wallrj closed this as completed Oct 31, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants