Skip to content
This repository has been archived by the owner on Mar 25, 2024. It is now read-only.

Figure out namespacing #17

Open
cloudnautique opened this issue Mar 14, 2019 · 3 comments
Open

Figure out namespacing #17

cloudnautique opened this issue Mar 14, 2019 · 3 comments

Comments

@cloudnautique
Copy link
Contributor

cloudnautique commented Mar 14, 2019

The namespacing of the operator is slightly off. It only watches the namespace it is deployed into. Additionally the k8s clients ignore the namespace parameter when listing the Custom Resources.

@cloudnautique cloudnautique reopened this Apr 26, 2019
@cloudnautique cloudnautique changed the title Figure out namespacing clients Figure out namespacing Apr 26, 2019
@luthermonson
Copy link
Contributor

@cloudnautique this should be closed now, the wrangler port will fix all your concerns with name spacing. We can go over to confirm but here is that PR: #24

@docteurklein
Copy link

Based on what I experience with d28d2f2, I still think the controller only observes only 1 namespace if you don't pass --namespace. it will default to default:

run with terraform-controller --debug

time="2020-02-04T08:59:46Z" level=info msg="Booting Terraform Controller, namespace: default" func=main.run file="/go/src/github.com/rancher/terraform-controller/main.go:88"

Seems like I don't see the behavior described in the readme: https://github.com/rancher/terraform-controller#namespace.

Am I missing something ?

@k0da
Copy link
Contributor

k0da commented Dec 3, 2020

@docteurklein #76 should fix this

k0da added a commit to k0da/terraform-controller that referenced this issue Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants