-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to deploy kctf-operator #356
Comments
Ah, Eduardo just updated the operator to a newer version I think. @sirdarckcat can you take a look? |
Oh, sorry, I forgot about that document Here's the script we used, it can be ran after you activate kCTF. https://github.com/google/kctf/blob/v1/kctf-operator/build-and-deploy-operator.sh |
Also this https://github.com/google/kctf/blob/v1/.github/workflows/update-images.yaml#L178 explains what to install |
Thanks for the pointers! It's much appeciated! However I am looking into deploying the operator on a kubernetes cluster on premise. So I assume the |
hmm, well, some things wont work, but try it! add a namespace called that said, it's probably better for you to just send a pull request and modify the |
Will try it out! Thanks! Also mentioning this here #342 as it seems related. I will keep you informed of the progress here. |
yep, I agree. I think we can mark this as a duplicate of 342. |
Hey guys,
I was looking for instructions on how to build and deploy the kctf-operator and stumbled across this documentation page https://github.com/google/kctf/blob/v1/docs/kctf-operator.md however it seems that it's out of date.
Even though the instructions recommend using operator-sdk v0.18.x, when I try to generate the CRDs I am getting the following error:
FATA[0000] failed to read config: error unmarshalling project configuration: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go struct field Config.layout of type string
Can you please advise on the matter?
The text was updated successfully, but these errors were encountered: