Skip to content
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

Walkthrough Error: the path "examples/v0.8.0/httpscaledobject.yaml" does not exist #1026

Closed
ImIOImI opened this issue May 13, 2024 · 2 comments · Fixed by #1032
Closed

Walkthrough Error: the path "examples/v0.8.0/httpscaledobject.yaml" does not exist #1026

ImIOImI opened this issue May 13, 2024 · 2 comments · Fixed by #1032
Labels
bug Something isn't working

Comments

@ImIOImI
Copy link

ImIOImI commented May 13, 2024

Report

The documentation on the walkthrough isn't correct. It presupposes a manifest being located at examples/v0.8.0/httpscaledobject.yaml exists, but doesn't. Furthermore, the httpscaledobject is installed in the previous step with the xkcd application

Expected Behavior

I should be able follow the walkthrough and successfully setup the xkcd application without getting any errors.

Actual Behavior

When running kubectl create -n $NAMESPACE -f examples/v0.8.0/httpscaledobject.yaml I get the following error:
the path "examples/v0.8.0/httpscaledobject.yaml" does not exist

Steps to Reproduce the Problem

Follow the steps in the walkthrough

Logs from KEDA HTTP operator

N/A

HTTP Add-on Version

0.8.0

Kubernetes Version

1.28

Platform

Microsoft Azure

Anything else?

No response

@ImIOImI ImIOImI added the bug Something isn't working label May 13, 2024
@JorTurFer
Copy link
Member

Hello,
You're totally right, we didn't upgraded the example by mistake, let me open a PR with the fix

@JorTurFer
Copy link
Member

These are the required changes, thanks for reporting it 😄
#1032

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants