-
Notifications
You must be signed in to change notification settings - Fork 6
http-add-on with istio #29
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
base: main
Are you sure you want to change the base?
Conversation
e7d81cf
to
40ca37b
Compare
|
||
Let's expose it using istio `VirtualService`. | ||
``` | ||
$ kubectl apply -f https://raw.githubusercontent.com/kedify/examples/main/samples/http-add-on_with_istio/manifests/istio.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not yet available on that link until this PR merges, for now available under
https://raw.githubusercontent.com/wozniakjan/kedify-examples/http-add-on_with_istio/samples/http-add-on_with_istio/manifests/istio.yaml
26534d3
to
6a29e34
Compare
Signed-off-by: Jan Wozniak <[email protected]>
6a29e34
to
53bbd8b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
|
||
##### Step 4: Start autoscaling | ||
|
||
First we will need to create `HTTPScaledObject` to tell KEDA and http-add-on what metrics to use and which `Deployment` to scale |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once we have the build with kedify-http
scaler, let's start using ScaledObject in favor of HTTPScaledObject
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed the examples in this repo all use upstream KEDA and are without Kedify agent, so I followed that pattern too.
I will make sure to list Kedify agent as a prerequisite and reference this:
https://kedify.io/resources/blog/kedify-keda-powered-public-beta-launch-announcement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, from now go on, we should use the Kedify approach, also in the examples.
This PR introduces a guide on how to use upstream KEDA and http-add-on together with istio.