-
Notifications
You must be signed in to change notification settings - Fork 20
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
Document labels used by Okteto pods #240
Comments
@RinkiyaKeDad Should we move this issue to the docs repo? Where is the best place to document those labels? |
Yes. Let's first create an issue on github.com/okteto/docs and there we can discuss where to document this! |
I've opened an internal backlog item here for now to help me track and prioritize this request. @RinkiyaKeDad let me know when you open that issue so I can cross-link 🙏 cc @jmacelroy it looks like this will move to the docs repo but likely still needs |
@RinkiyaKeDad I transferred the issue from https://github.com/okteto/okteto as you requested so we can discuss how to achieve this 😄 |
@omnomagonz I think we can cover this in docs most quickly and just with this issue. @RinkiyaKeDad Did you have some ideas on where and how to best document this. |
I would suggest first documenting this on the community website and then moving it to the docs once we figure out what the appropriate section for this could be. @vitobotta do you mind framing this as a question and posting it on community.okteto.com? 😄 more context: https://okteto.slack.com/archives/C02SX9665RP/p1667210769186039 |
Is your feature request related to a problem? Please describe.
Documentation request
Describe the solution you'd like
In my case, I use a wrapper around some K8s tools including Okteto to abstract some complexity, and am also using KEDA autoscaling to scale my app. When I start Okteto, the autoscaler interferes because it automatically starts its own non-Okteto pods, so traffic is then split between Okteto pods and the autoscaler pods, causing problems and confusion. For this reason, I changed my CLI so that before starting Okteto it patches the services so that they send traffic only to the Okteto pods, ignoring the autoscaled pods. So I can work with Okteto just fine.
This wasn't documented, so I had to figure out that Okteto labels the pod for the main service with the label "interactive.dev.okteto.com" and the additional services (as specified in the manifest) with "detached.dev.okteto.com".
By patching my services to use these labels during an Okteto session, I no longer have problems due to the autoscaling.
Describe alternatives you've considered
I couldn't think of an alternative
The text was updated successfully, but these errors were encountered: