docs: Introduce troubleshooting guide for Azure Service Bus #1269
Conversation
✅ Deploy Preview for keda ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Thank you for your contribution! 🙏 We will review your PR as soon as possible.
Learn more about:
|
|
What do you think about this idea @zroubalik / @JorTurFer |
tomkerkhove
changed the title
|
Maybe we can create a new secction for these stuff, and include FAQ and troubleshooting pages. Troubleshooting info looks quite fragmentated between FAQ, troubleshooring, and now in page |
|
Just to clarify, I'd move to a versioned section, because fixes related with v2.X can apply to v2.Y or not |
|
I agree and that is also why I added this:
However, I am not sure if we should do it now already or in the future. Currently I think we should just add this to scalers for now and once we have more scenarios we can look at how we can support it and what the needs are (instead of assuming) |
|
yeah, definitivelly! |
I think that it's interesting in general |
|
@zroubalik @JorTurFer as mentioned above, wanted to know if you think it's the right place to start before applying it everywhere. I think that is not fully answered yet, once it is I will expand it to all versions |
|
Shall we merge this or do we look for alternative ways @zroubalik @JorTurFer ? |
|
We can merge it IMO (but add it to v2.13 too) |
|
Ugh I love GitHub codespaces messing up DCO |
Signed-off-by: Tom Kerkhove <[email protected]>
tomkerkhove
force-pushed
the
tomkerkhove-patch-1
branch
from
eeadf02
to
8b7ad4c
Compare
Signed-off-by: Tom Kerkhove <[email protected]>
Based on kedacore/keda#5227, I had a quick idea to start introducing troubleshooting guides to reduce the load on maintainers/community and document recurring issues.
Currently this is added to the same page as the scaler, but we should integrate scalers in to our existing "troubleshooting" section over time.
Checklist
Relates to kedacore/keda#5227