Skip to content

Conversation

@hugobarauna
Copy link
Member

The generated YAML now works out of the box, all resources deploy to the user's current namespace without requiring prior setup.

Users can customize the target namespace as needed.

Before this PR, when I tried to test locally per the instructions, they didn't work out of the box.

The generated YAML now works out of the box, all resources deploy to the user's current namespace
without requiring prior setup.

Users can customize the target namespace as needed.
@hugobarauna
Copy link
Member Author

If we want, we could leave a comment about setting a k8s namespace.

But I thought this was not needed, assuming this YML is a starting point that the user will likely need to customize to their own context, which could include changes beyond just the namespace.

@hugobarauna hugobarauna merged commit 614c808 into main Jan 31, 2026
4 checks passed
@hugobarauna hugobarauna deleted the hb-improve-k8s-instructions branch February 1, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants