https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# hobbyfarm
a
This message was deleted.
l
thank you so much for reply, I have managed to create users including admin
but now I have another problem
after login to admin panel as admin I don't see anything to edit or create
after login to ui I see only this
I have applied resources from documentation example https://hobbyfarm.github.io/docs/architecture/resources/
thank you in advance for any suggestions
w
do you see any errors in the logs in the gargantua pod, when you refresh the page after logging in?
l
thank you for reply, currently logs from gargantua are showing some problem with parsing time
Copy code
I1229 07:53:57.112848       1 sessioncontroller.go:74] Enqueueing ss hobbyfarm/sample-session
I1229 07:53:57.112936       1 sessioncontroller.go:111] processing ss in ss controller: hobbyfarm/sample-session
I1229 07:53:57.112957       1 sessioncontroller.go:138] reconciling session sample-session
E1229 07:53:57.113007       1 sessioncontroller.go:121] parsing time "" as "Mon Jan _2 15:04:05 MST 2006": cannot parse "" as "Mon"
I1229 07:53:57.113272       1 sessioncontroller.go:124] ss processed by session controller sample-session
I1229 07:53:57.358863       1 scheduledeventcontroller.go:85] Enqueueing se hobbyfarm/testing-se
I1229 07:53:57.358933       1 scheduledeventcontroller.go:122] processing se in se controller: hobbyfarm/testing-se
I1229 07:53:57.358957       1 scheduledeventcontroller.go:579] reconciling scheduled event testing-se
I1229 07:53:57.367177       1 scheduledeventcontroller.go:137] se processed by scheduled event controller testing-se
Copy code
sessioncontroller.go:121] parsing time "" as "Mon Jan _2 15:04:05 MST 2006": cannot parse "" as "Mon"
only one place where I have specified time is Session yaml manifest
Copy code
status:
    paused: false
    active: true
    finished: false
    start_time: "2006-01-02 15:04:05.999999999 -0700 MST"
    end_time: "2025-01-02 17:04:05.999999999 -0700 MST"
f
Please delete the session ressource. You dont need it. Session ressources are only handled by gargantua (the backend) and never need to be created manually.
Regarding the "empty" Admin dashboard: You will need give the admin account permissions to all ressources. Was any "Role" resource created in the desired hobbyfarm ns?
If no role was created create one like this: https://github.com/hobbyfarm/hobbyfarm/commit/65853a45574ff56fb44dac7b5b7ec70e8600a7ec And add a rolebinding matching to your created user
l
Awesome, thank you so much, I will try this right now
f
Perfect. i will update the docs on this issue.
l
At the end I will hope that I will be able also to contribute to this project 😄
f
Are "Roles" created? You can with a gargantua flag, which is not enabled by default i believe
l
I have two roles in 
hobbyfarm
ns
kubectl get roles -n hobbyfarm NAME CREATED AT gargantua 2022-12-08T153340Z hobbyfarm-admin 2022-12-08T153340Z
Copy code
kubectl get roles -n hobbyfarm -o yaml
apiVersion: v1
items:
- apiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>
  kind: Role
  metadata:
    annotations:
      <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: hobbyfarm
      <http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: hobbyfarm
    creationTimestamp: "2022-12-08T15:33:40Z"
    labels:
      <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: Helm
    name: gargantua
    namespace: hobbyfarm
    resourceVersion: "16201"
    uid: 697c895b-4c03-4d15-a367-cf3536e8954d
  rules:
  - apiGroups:
    - ""
    resources:
    - '*'
    verbs:
    - '*'
  - apiGroups:
    - <http://coordination.k8s.io|coordination.k8s.io>
    resources:
    - leases
    verbs:
    - '*'
  - apiGroups:
    - <http://hobbyfarm.io|hobbyfarm.io>
    resources:
    - '*'
    verbs:
    - '*'
  - apiGroups:
    - <http://terraformcontroller.cattle.io|terraformcontroller.cattle.io>
    resources:
    - '*'
    verbs:
    - '*'
  - apiGroups:
    - <http://rbac.authorization.k8s.io|rbac.authorization.k8s.io>
    resources:
    - roles
    - rolebindings
    verbs:
    - '*'
- apiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>
  kind: Role
  metadata:
    annotations:
      <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: hobbyfarm
      <http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: hobbyfarm
    creationTimestamp: "2022-12-08T15:33:40Z"
    labels:
      <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: Helm
      <http://rbac.hobbyfarm.io/managed|rbac.hobbyfarm.io/managed>: "true"
    name: hobbyfarm-admin
    namespace: hobbyfarm
    resourceVersion: "16200"
    uid: 39b27d12-c34a-42ea-abcf-97eba6a29972
  rules:
  - apiGroups:
    - <http://hobbyfarm.io|hobbyfarm.io>
    resources:
    - '*'
    verbs:
    - '*'
  - apiGroups:
    - <http://rbac.authorization.k8s.io|rbac.authorization.k8s.io>
    resources:
    - roles
    - rolebindings
    verbs:
    - '*'
f
perfect. the "hobbyfarm-admin" role is the one you need to define in your rolebinding matching to your user
l
awesome, this looks like solution for my problem
I am checking this
ok, this works perfect but I see some other Admin UI error
it seems that list scenarios can't be fetched or listed
f
I guess you have created a scenario as well? Try to delete it please
Or can you show what thebackend sends back on the request fetching the scenarios? 🙂
l
yes, you were right
Scenario from example was messing my setup
after removing it, it seems to work fine
f
can you tell me where you havce taken the scenario from? the docs?
l
beause I didn't have a admin role, I was thinking that there missing some resources
so I tried to deploy it from example
f
I am fixing the docs right now!
l
awesome, thank you so much
I will test it as well and submit also some fixes or changes
finally I can try and use this project
f
nice! 🙂
l
It looks awesome to me, at the end I think that this might be added to Helm chart
f
nah, we want to rely on gargantua to create this. But yeah there should be some automation done here
3 Views
Open in Slack
PreviousNext
Powered by