I'm thinking about building a k8s operator for running Woodpecker-CI, but I have some questions.

[allanger]

Hi,

I've tried Woodpecker not so long ago, and I think it's a great project.

I thought that it might make sense to have a Kubernetes operator that runs the whole Woodpecker setup using CRDs.
My idea for a first version is to create several CRDs:

• Server
• Agent
• Project
• Secret

And then it should be possible to run the operator and control the whole Woodpecker as code.

The only problem I have, is that I can run a server, but to configure Secrets, Projects, and Agents, I'll need a user on the server, and it means that I have to create a Server CR, wait for the server to be up and running, log in, and then add this account to the server CR, so it can manage other entities, and it doesn't sound like a good setup, for at least two reasons:

1. User should be able to use only k8s tools to run something in k8s, so users shouldn't be required to log in using the browser, in order to continue setting things up
2. In my opinion, git accounts are personal accounts, and bots shouldn't be added as git users to woodpecker. It's arguable, but if you have a bot user, you can at least hide your identity behind this bot when running pipelines. So bot should be only able to configure Woodpecker, but then it doesn't make sense to have a git account for them.

So, I think for my use-case, it would be perfect to have an admin account that can only configure Woodpecker.

Hence the question, Is there a way I could achieve it now? And if not, maybe we can think about implementing something like that, I can try helping with the code, if you have an idea what it could look like.

Thanks

[pat-s]

Hey!

Since you didn't mention it, are you aware of https://github.com/woodpecker-ci/helm?

[allanger]

Yes, I'm using it at the moment. But it's not solving my problem.

[allanger]

Alright, I think I've missed this var somehow "WOODPECKER_AGENT_SECRET". I guess it should be what I was looking for