Use Istio 1.0.0.#1771
Conversation
|
/test pull-knative-serving-unit-tests |
|
Awesome, thanks for pulling this in so quickly. |
| Our goal here is to allow sidecar injection for Pods created by Knative, and | ||
| nothing else. This template is used in integration tests and also released as | ||
| an Istio-one-line-installation so that our users don't have to go through a lot | ||
| of steps to install Istio. |
There was a problem hiding this comment.
It would be good to make note of whether Istio installed as configured here is a production-ready configuration or more of a "kick-the-tires" configuration. I honestly do not know, but it would be good to call it out.
There was a problem hiding this comment.
This comment is non-blocking, btw.
|
Istio 1.0 is installing fine for me as packaged here, but I'm having a little trouble getting Knative to install on top of it: |
|
Maybe I need to take #1725 into account? Seems it. I'm having trouble building |
|
@krancour we recently changed getting started to use 0.1.0 -- you can find the old url in the PR https://github.com/knative/docs/pull/287/files . We should still document it somewhere. |
|
@tcnghia thanks. This all checks out for me on minikube. On Azure, I encounter known issues + a new issue of the istio-galley crash looping because of failed health checks. I do not assume that to be a problem with this change though. |
The new issue was user error. So this change checks out on at least minikube and Azure. |
|
/approve |
|
Manually tested with the eventing e2e tests in knative/eventing#304 /lgtm |
| @@ -9,7 +10,6 @@ cd istio-${ISTIO_VERSION} | |||
| helm template --namespace=istio-system \ | |||
| --set sidecarInjectorWebhook.enabled=true \ | |||
| --set sidecarInjectorWebhook.enableNamespacesByDefault=true \ | |||
| --set global.proxy.image=proxyv2 \ | |||
There was a problem hiding this comment.
just curious, why do we not need to set "global.proxy.image=proxyv2" ?
There was a problem hiding this comment.
The PR is updated with the explanation #1771 (comment)
| containers: | ||
| - name: istio-proxy | ||
| # PATCH #2: Add a prestop sleep. |
There was a problem hiding this comment.
I guess we may still need to keep this PATCH until we fix issue #1370
There was a problem hiding this comment.
I think we can't keep that because we don't have control over how the user may install Istio. I leave the bug open to track & fix that issue, which may or may not be there anymore (since it was an issue with Istio 0.6)
(see comment in #1771 (comment))
|
/lgtm |
|
@evankanderson can you please /approve? thanks |
| apiVersion: autoscaling/v2beta1 | ||
| kind: HorizontalPodAutoscaler | ||
| metadata: | ||
| name: istio-pilot |
There was a problem hiding this comment.
Needs namespace: istio-system
There was a problem hiding this comment.
Bummer, but this is upstream https://github.com/istio/istio/blob/8daa232df6ef7cdbb2987de1187255b14e3c3989/install/kubernetes/helm/istio/charts/pilot/templates/autoscale.yaml
(compare that to https://github.com/istio/istio/blob/8daa232df6ef7cdbb2987de1187255b14e3c3989/install/kubernetes/helm/istio/charts/mixer/templates/autoscale.yaml)
I'll file a bug to Istio.
Nice catch, thanks.
There was a problem hiding this comment.
What happens if we submit this without patching namespace?
Is this safe to submit, or do we need the upstream to be fixed first? Since this is an HPA, it probably just means that pilot won't scale-out if needed.
(BTW, you linked to the same file twice.)
|
I'll approve once @scothis' comment is resolved.
…On Thu, Aug 2, 2018 at 2:49 PM Scott Andrews ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In third_party/istio-1.0.0/istio.yaml
<#1771 (comment)>:
> + kind: Deployment
+ name: istio-telemetry
+ metrics:
+ - type: Resource
+ resource:
+ name: cpu
+ targetAverageUtilization: 80
+---
+
+---
+# Source: istio/charts/pilot/templates/autoscale.yaml
+
+apiVersion: autoscaling/v2beta1
+kind: HorizontalPodAutoscaler
+metadata:
+ name: istio-pilot
Needs namespace: istio-system
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1771 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHlyN6uN4MMhAklAYYm0srEKCY2jfa7Gks5uM3PNgaJpZM4Vpukh>
.
--
Evan Anderson <argent@google.com>
|
evankanderson
left a comment
There was a problem hiding this comment.
I'm assuming that we're planning to change our documentation to say "Install istio via their instructions."?
| apiVersion: autoscaling/v2beta1 | ||
| kind: HorizontalPodAutoscaler | ||
| metadata: | ||
| name: istio-pilot |
There was a problem hiding this comment.
What happens if we submit this without patching namespace?
Is this safe to submit, or do we need the upstream to be fixed first? Since this is an HPA, it probably just means that pilot won't scale-out if needed.
(BTW, you linked to the same file twice.)
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evankanderson, krancour, tcnghia The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I also added some explanation of the Helm options we used for generating
istio.yaml.I dropped the
sleep 20patch (see #1370), since we can't really dictate our yaml on user's clusters --- it doesn't make sense to keep carrying the patch. We'll leave the bug open to investigate if the issue is still around (many things have changed since we added thatsleep 20) and find a different solution if it still lingers. After this change this yaml is just for a convenience one-liner without asking users to go through helm installation or Istio installation docs.I dropped the
global.proxy.image=proxyv2option because that's the default now.Will follow up with more documentation in
knative/docsto explain what we expect from Istio sidecar injection setup so that users already having Istio would know how to configure it to work with Knative./assign @ZhiminXiang
/assign @evankanderson
/cc @scothis
/cc @krancour