-
Notifications
You must be signed in to change notification settings - Fork 26
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
Install knative #177
base: master
Are you sure you want to change the base?
Install knative #177
Conversation
@mckornfield I'm trying to under stand this and doing some test, I got some question.
When I check the
Seems we need to set the ingress to make it work, the URL is http://hello.knative-serving.svc.cluster.local for the hello fun, but I don't think we can access it because of some problem? Some other error log:
BTW, knative seems promising, I tried to manually create another fun and deploy it to the dev, everything goes well except the last step to route the traffic, just like your |
@mckornfield did you try to visit the function by the URL? http://hello.knative-serving.svc.cluster.local |
for your last question, I just port forwarded to test, assuming we'd use a mapping file |
@mckornfield thank you for the quick response, I think we are close to being able to use faas, once we solve the mapping/ingess problem, right? |
It is definitely more complicated, my port-forwarding might have been over-simplified... I can look at what it takes to hook ambassador up to it |
wonder if this will work, though 3-4 years old https://github.com/bbrowning/knative-ambassador-ingress |
@dadiorchen Just trying to install this project above and follow some tutorials lead me to some failed installs... Wonder if there's a semi-recent way to connect ambassador to knative lol |
@mckornfield is it possible to use the default ingress ( I guess it is the istio) to make things right as the first step so we can play with to understand the thing, and if it is possible that we use a two level gateway to put the knative+istio behind the ambassador, anyway, it is helpful to just run it successfully |
🤔 I think that would require setting up an istio ingress too, but I'm not sure we want two of them/ if that's just as much work to set up |
I'm determined to get it working, just the ambassador docs are really anemic lol https://www.getambassador.io/docs/emissary/latest/howtos/knative |
part of our problem might be that we're on an old version of ambassdor... it's now called emissary-ingress 😆
|
@mckornfield I'm okay with upgrading the ambassador, what do you think? |
Probably something worth doing independent of this, but I worry for backwards incompatible changes hehe |
@mckornfield do you mean a sperate env for this? It that's you are saying, I think so too, should we open a new cluster for test goal on this? The dev env is getting more and more heavy and hard to change. |
Separate env would be part of it, but at some point we'd need to upgrade the older clusters. I just wonder if bumping ambassador to emissary would be a good thing to do first before trying to add knative |
I will be happy if we can upgrade the ambassador to a newer version, even pay some cost of learning and fixing work! |
No description provided.