Issue getting stackset-controller running about stackset-controller

[stormmore]

OK I have figured out what the issue is / was. Looks like the documentation for RBAC has some old references to applications (stacks) and applicationstacks (stacksets).

My RBAC config is now:

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  creationTimestamp: 2018-11-16T20:21:46Z
  name: stackset-controller
  resourceVersion: "69399344"
  selfLink: /apis/rbac.authorization.k8s.io/v1/clusterroles/stackset-controller
  uid: 3dc5925c-e9dd-11e8-8400-06fe3d4492c6
rules:
- apiGroups:
  - zalando.org
  resources:
  - stacks
  - stacks/status
  - stacksets
  - stacksets/status
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - patch
  - delete
- apiGroups:
  - apps
  resources:
  - deployments
  verbs:
  - get
  - list
  - create
  - update
  - patch
  - delete
- apiGroups:
  - extensions
  resources:
  - ingresses
  verbs:
  - get
  - list
  - create
  - update
  - patch
  - delete
- apiGroups:
  - ""
  resources:
  - services
  verbs:
  - get
  - list
  - create
  - update
  - patch
  - delete
- apiGroups:
  - autoscaling
  resources:
  - horizontalpodautoscalers
  verbs:
  - get
  - list
  - create
  - update
  - patch
  - delete
- apiGroups:
  - ""
  resources:
  - endpoints
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - patch

[mikkeloscar]

@stormmore Cool that you are trying out the stackset-controller! You say you don't get any logs at all, could you share the manifests you use to deploy the controller? and the output of kubectl logs stackset-controller-... (or is there no logs AT ALL?)

[stormmore]

The only manifest I am trying to deploy is the Nginx one that is in the repo docs. Figured that would be a good test to see if the controller was working or not. As for logs it is literally nothing output from kubectl logs stackset-controller-84cb74f794-l2dsz.

That said, when I ran it locally, I did get errors about not having access to the kubernetes API so I know that the container can output logs.

[szuecs]

@stormmore do you have any admission webhooks that are able to change objects installed?
Interesting errors in the logs, we should check.

[stormmore]

Yes, I am using KUbeDB for my DB operators.

[mikkeloscar]

Awesome, thanks for looking into this. I opened a PR to fix the example: #82

[mikkeloscar]

I consider this fixed! :)