-
Notifications
You must be signed in to change notification settings - Fork 49
Conversation
10f6ddd
to
b7a02d0
Compare
docs are going in a separate PR ? |
b7a02d0
to
d2f67d0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general LGTM, except the comment. Also e2e tests needs to be added.
d2f67d0
to
439b708
Compare
We have decided to name this component |
7eb6986
to
0b575ff
Compare
0b575ff
to
7804932
Compare
@surajssd do you mind rebasing before I review (to get rid of fixup commits)? |
3c1fa21
to
0ff1ff5
Compare
@invidian done :-) |
@invidian PTAL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall things looks OK to me, however, I would re-organize and improve commit messages, as there is a lot of things going in regards to how we manage the namespaces for the components, which seems like something, which should be definitely described with the reasoning behind. It could even be done in separate pull request to simplify and separate the review comments.
@surajssd can we move changes related to Helm and other components into separate PR, as they are not related to istio-operator (though I'm aware that this PR, so istio-operator depends on those changes).
assets/components/cert-manager/manifests/templates/namespace.yaml
Outdated
Show resolved
Hide resolved
assets/components/prometheus-operator/manifests/templates/prometheus-operator/namespace.yaml
Outdated
Show resolved
Hide resolved
|
||
Table of all the arguments accepted by the component. | ||
|
||
Example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this Example mean here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I am not sure what they mean. It is a remnant of the copy-paste of the skeleton from other components.
0ff1ff5
to
5363720
Compare
I think I can elaborate on the commits but creating a new PR will only prolong this work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lovely work @surajssd 🎉
Generally LGTM.
Please take a look into creating a separate PR for allowing helm to create release namespace.
assets/components/cert-manager/manifests/templates/namespace.yaml
Outdated
Show resolved
Hide resolved
@surajssd On second thoughts, its better not use the helm feature All it does is create a namespace object on the fly and seeing that we have a use case where we patch the namespace with labels, it becomes a two step operation. I would rather use the existing code to create/update the release namespace and not depend on helm for it. |
https://yard.lokomotive-k8s.net/builds/26675
Ugh, it seems the test needs to be modified... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some nits, otherwise LGTM. The only missing bit is, that either the e2e test needs to be modified or we need to add a lokomotive name label to the istio namespace (the latter is definitely easier).
7e971a2
to
616e444
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
a7ba6c6
to
6763446
Compare
Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
Adds ServiceMonitor configs for the control plane and istio-proxy sidecars which is toggled by a variable `enable_monitoring`. Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
- Adds e2e test to verify if pods are up and running. - Adds test to verify if the metrics are scraped. Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
6763446
to
893a1f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, another component. Great work @surajssd
Something is wrong with the istio release bundle, which is downloaded from https://github.com/istio/istio/releases/tag/1.7.0 : $ ll
drwxr-x---@ - surajd 22 Aug 0:30 istio-1.7.0/
.rw-rw-r--@ 47M surajd 22 Aug 6:30 istio-1.7.0-linux-amd64.tar.gz The image tag is $ cat istio-1.7.0/manifests/charts/istio-operator/values.yaml
hub: gcr.io/istio-testing
tag: latest
operatorNamespace: istio-operator
# Used to replace istioNamespace to support operator watch multiple namespaces.
watchedNamespaces: istio-system
waitForResourcesTimeout: 300s
# Used for helm2 to add the CRDs to templates.
enableCRDTemplates: false
# revision for the operator resources
revision: ""
# Operator resource defaults
operator:
resources:
limits:
cpu: 200m
memory: 256Mi
requests:
cpu: 50m
memory: 128Mi |
@surajssd this is for the operator image, but yeah, it's weird that they don't pin the version. Using "testing" image registry is weird too ( I'll open an upstream issue about it, but I don't think this should block merging this PR. EDIT: Created istio/istio#26920. |
@invidian looks like an interesting project. Please note in the pending Istio 1.8, there is a make target that generates a proper manifest using helm template for the operator:
The pending 1.8 manifest is in a lot better shape than what was shipped in Istio 1.6 👍 Although what you have should be fine. Thanks for adopting Istio in your project and reporting the pinning defect. Cheers, |
Fixes #687
Usage
Install using
lokoctl component apply experimental-istio-operator
:Then to test it on an app, clone this repo and goto
configs/bookinfo
dir and run following commands:kubectl create ns bookinfo kubectl label namespace bookinfo istio-injection=enabled helm install bookinfo --namespace bookinfo .
TODOs
Test:
Other: