How to run on a kubernetes repo? #28097
-
What would you like help with?I would like help with my configuration How are you running Renovate?Self-hosted If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.Bitbucket, latest docker image Please tell us more about your question or problemI'm trying to test RenovateBot on a Bitbucket repo that mainly consists of Kubernetes manifests (for deploying with FluxCD). So far I'm doing: My configuration (stored in It looks like this probably isn't checking chart/image versions in the YAML Kubernetes manifests. FWIW, I found the docs for configuration to be very lacking in introductory material. The "Getting Started - Self-Hosted Example" gives inconsistent config file names (the docker example uses
This failed cryptically, so I replaced with:
This ran, but I can't seem to tell if it is actually working (and I'm pretty sure not all of the repo's manifests are using latest upstream image versions etc). How do I check? Logs (if relevant)
Full logs: (click to expand) |
Beta Was this translation helpful? Give feedback.
Answered by
benjimin
Mar 26, 2024
Replies: 3 comments 7 replies
-
|
Pick one way to configure, capture the full debug logs, paste them here. You picked one of the few managers to start which has no default fileMatch (kubernetes) whereas for others it would normally "just work". |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Full logs pasted. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsIf you're running self-hosted, run with Insufficient logsSelect me to read instructionsIf you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section. Formatting your logsSelect me to read instructionsPlease put your logs in a If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Full logs pasted. |
Beta Was this translation helpful? Give feedback.
-
|
The kubernetes part was not parsed. You may need to add it to a config.js or stringify it as part of RENOVATE_CONFIG |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
@rarkins how can you tell (that it wasn't parsed)? Is there something specific in the logs I should log for (that perhaps isn't captured by just doing I already tried to "stringify it as part of RENOVATE_CONFIG", by replacing I've also tried Next I tried including This unfortunately produced the output (and with no further detail): I'm not sure what I'm missing. How would I convert this config into javascript? |
Beta Was this translation helpful? Give feedback.
-
|
Update: I had my local copy of Would still be keen to fix why stringify didn't work? (Because env vars would be more convenient as a deployment method.) |
Beta Was this translation helpful? Give feedback.
-
|
What I'm seeing is that they are being parsed as strings instead of JSON objects. Escaping env variables is hard and people sometimes end up with too many or too little escaping, and it's hard to diagnose from afar. There are some examples in https://docs.renovatebot.com/config-overview/#environment-variable-examples to look at |
Beta Was this translation helpful? Give feedback.
-
|
Aha, seems all I needed was So for the full example: Thanks @rarkins for the support! |
Beta Was this translation helpful? Give feedback.
Answer selected by
benjimin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Aha, seems all I needed was
RENOVATE_KUBERNETES={"fileMatch":["\\.yaml$"]}.So for the full example:
Thanks @rarkins for the support!