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

Workflows install fails if fission is not installed in the "fission" namespace #69

Closed
soamvasani opened this issue Oct 19, 2017 · 3 comments
Closed

Workflows install fails if fission is not installed in the "fission" namespace #69

soamvasani opened this issue Oct 19, 2017 · 3 comments
Labels
area/deployment bug
Milestone
0.3.0

Comments

@soamvasani
Copy link
Member

No description provided.

@soamvasani soamvasani added this to the beta milestone Oct 19, 2017
@erwinvaneyk
Copy link
Member

Proposed solution: change helm chart to assume by default that fission is located in the same as where fission workflows will be installed. To have workflows live in a seperated ns, the user will need to update the helm value to point to the ns with fission deployment it wants to use.

@erwinvaneyk erwinvaneyk modified the milestones: beta, 0.2.0 Nov 24, 2017
@soamvasani
Copy link
Member Author

soamvasani commented Nov 24, 2017 •
edited
Loading

Yeah, ok, let's do that. It's not ideal, since the user controls installation namespaces, but I can't think of anything better.

@erwinvaneyk
Copy link
Member

Fixed in #90 (which depends on fission/fission#413 in Fission)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/deployment bug
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
2 participants
@erwinvaneyk @soamvasani