namespace hardcoded to default about spekt8 HOT 20 OPEN

+1

from spekt8.

+1 when I deploy with different namespace, I can not access to the cluster info

from spekt8.

+1

from spekt8.

Please do this

from spekt8.

+1

from spekt8.

Also unless I'm reading it wrong, wouldn't this RBAC CRB (https://github.com/spekt8/spekt8/blob/master/fabric8-rbac.yaml#L12) allow full access to any pod, not just the spekt8 one?

from spekt8.

+1 this is a dealbreaker to even eval this. I can't see any information for stuff in any namespace outside of default

from spekt8.

+1 this is a dealbreaker to even eval this. I can't see any information for stuff in any namespace outside of default

it is pretty simple to fork and add another namespace at least to check it out, only took a couple of minutes.

from spekt8.

@mickoallen Can you push the changes you made back to your fork so we can see how you did this?

from spekt8.

For anyone curious. I forked the repo, adjsuted the namespace value in k8sApi*.listNamespace* and replaced the vauld 'default' with 'mynamespace'. Built, deployed, but no go. I have less errors overall but this one I'm not sure how to handle.

console.error('SBO Downloader is unable to download the course, it is out of control issue.');

from spekt8.

@claywd > @mickoallen Can you push the changes you made back to your fork so we can see how you did this?

Sure, i fully cheesed it though, don't know how useful it is.
Shouldn't be hard to make it more configurable.

master...mickoallen:master

from spekt8.

@mickoallen dang... I dd exactly what you did already and I'm still getting that same error. Does it actually work for you? did you make any changes to the rbac?

from spekt8.

@claywd damn, i didn't make any changes there. Also if i remember correctly i only used it against minikube...

from spekt8.

@mickoallen hmm.. I mean I am using it against AKS but its hard to believe that would make a difference when all the permissions are already setup. @cbanigan might take a look for us soon. Hopefully he can see what I'm missing.

from spekt8.

+1 to this, also having this problem

from spekt8.

+1

from spekt8.

+1 same issue. Doesn't seem like author is going to address this

from spekt8.

+1

from spekt8.

+1

from spekt8.

I have forked the code and make namespace modifiable via environment value, you just have to pass NAMESPACE as env value and using sanarena/spekt8 as image url.

As an example:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: spekt8
spec:
  selector:
    matchLabels:
      component: spekt8
  replicas: 1
  template:
    metadata:
      labels:
        component: spekt8
    spec:
      containers:
        - name: spekt8
          image: sanarena/spekt8
          ports:
            - containerPort: 3000
          env:
          - name: NAMESPACE
            value: sanarena

from spekt8.