nats-io / nats-streaming-operator

NATS Streaming Operator
Apache License 2.0
174 stars 44 forks source link

Can't install `natscluster` and `natsstreamingcluster` into namespace #33

Closed exu closed 5 years ago

exu commented 5 years ago

nats.yaml

---
apiVersion: "nats.io/v1alpha2"
kind: "NatsCluster"
metadata:
  name: "nats-cluster"
  namespace: "nats"
spec:
  size: 3

nats-straming.yaml

---
apiVersion: "streaming.nats.io/v1alpha1"
kind: "NatsStreamingCluster"
metadata:
  name: "nats-streaming-cluster"
  namespace: "nats"
spec:
  size: 3
  natsSvc: "nats-cluster"

After kubectl apply there is no pods spawned in given namespace. Is there any workaround for this?

wallyqs commented 5 years ago

Did you deploy the operator via this snippet? Also if both operators are running are there any errors in the logs?

kubectl apply -f https://github.com/nats-io/nats-operator/releases/download/v0.3.0/deployment.yaml

# Install NATS Streaming Operator on default namespace
kubectl apply -f https://raw.githubusercontent.com/nats-io/nats-streaming-operator/master/deploy/default-rbac.yaml

kubectl apply -f https://raw.githubusercontent.com/nats-io/nats-streaming-operator/master/deploy/deployment.yaml
exu commented 5 years ago

Yes I was using following script to install

kubectl apply -f https://github.com/nats-io/nats-operator/releases/download/v0.3.0/deployment.yaml
kubectl apply -f https://raw.githubusercontent.com/nats-io/nats-streaming-operator/master/deploy/default-rbac.yaml
kubectl apply -f https://raw.githubusercontent.com/nats-io/nats-streaming-operator/master/deploy/deployment.yaml
kubectl create namespace nats
kubectl apply -f nats-cluster.yaml
kubectl apply -f nats-streaming-cluster.yaml

If I omit namespace everything installs ok in default namespace - when adding no resources are created

nats-operator-56c4974b7f-7dcp5            1/1     Running   0          4h
nats-streaming-operator-d5cbd6665-p97xd   1/1     Running   0          4h

k get all -nnats results in "No resources found"

wallyqs commented 5 years ago

looking at other issues like #34 , assuming this was resolved so closing for now. thanks