https://linen.dev logo
#kubernetes
Title
# kubernetes
a

Anton Podviaznikov

05/13/2022, 7:05 PM
hey everyone. I installed airbyte on k8s using guide. But I see some weird logs in
airbyte-worker
Copy code
Caused by: io.airbyte.workers.WorkerException: Failure executing: POST at: <https://10.0.0.1/api/v1/namespaces/etl/pods>. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:serviceaccount:etl:airbyte-admin" cannot create resource "pods" in API group "" in the namespace "etl": RBAC: <http://role.rbac.authorization.k8s.io|role.rbac.authorization.k8s.io> "airbyte-admin-role" not found.
	at io.airbyte.workers.process.KubeProcessFactory.create(KubeProcessFactory.java:138) ~[io.airbyte-airbyte-workers-0.38.3-alpha.jar:?]
	at io.airbyte.workers.process.AirbyteIntegrationLauncher.check(AirbyteIntegrationLauncher.java:80) ~[io.airbyte-airbyte-workers-0.38.3-alpha.jar:?]
	at io.airbyte.workers.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:53) ~[io.airbyte-airbyte-workers-0.38.3-alpha.jar:?]
	... 3 more
Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: <https://10.0.0.1/api/v1/namespaces/etl/pods>. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:serviceaccount:etl:airbyte-admin" cannot create resource "pods" in API group "" in the namespace "etl": RBAC: <http://role.rbac.authorization.k8s.io|role.rbac.authorization.k8s.io> "airbyte-admin-role" not found.
Any tips?
I think it's the same issue as here https://github.com/airbytehq/airbyte/issues/7211 I see that role wasn't created and I'm running k8s v1.21.10
resolved, issue was that I didn't have permissions to create new role
t

Thomas

05/20/2022, 8:17 AM
@Anton Podviaznikov How did you resolve it?
a

Anton Podviaznikov

05/20/2022, 3:50 PM
well,
airbyte-admin
was created originally and I didn't notice that error. It was created became my user didn't have permissions to create other users/roles in the cluster. So I asked for more permissions and it did work
8 Views