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.

Sign up for GitHub

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

Jump to bottom

"New Service" scenario #1021

Open
bartoszmajsak opened this issue Jul 11, 2022 · 0 comments
Open

"New Service" scenario #1021

bartoszmajsak opened this issue Jul 11, 2022 · 0 comments
Labels
Epic kind/enhancement Kind: New feature or improvement
Milestone
v0.6.0

Comments

@bartoszmajsak
Copy link
Contributor

bartoszmajsak commented Jul 11, 2022 •
edited
Loading

What can be improved

When starting a new service there are no k8s resources defined in the cluster. ike develop should let the developer start working locally on such a service and create necessary resources on the fly, including a "proxying" pod deployed.

Why

Without this feature, the tooling can't be used from the first day of development. At the moment istio-workspace supports workflows for existing services - so for changing existing code but not for prototyping new things. This limits the adoption and overall usefulness.
@bartoszmajsak bartoszmajsak added kind/enhancement Kind: New feature or improvement Epic labels Jul 11, 2022
@bartoszmajsak bartoszmajsak added this to the v0.6.0 milestone Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Epic kind/enhancement Kind: New feature or improvement
Projects
None yet
Milestone
v0.6.0
Development

No branches or pull requests
1 participant
@bartoszmajsak