When I deploy in my cluster I get this for istio-operator:
So everything seems fine until I get the pod logs:
$ k logs pod/istio-operator-769c594554-bctjh -n istio-operator
2021-07-18T09:52:58.674326Z info ControlZ available at 127.0.0.1:9876
2021-07-18T09:52:58.674485Z info leader election cm: istio-operator-lock
2021-07-18T09:52:59.725624Z info klog Throttling request took 1.040253723s, request: GET:https://172.20.0.1:443/apis/scheduling.k8s.io/v1?timeout=32s
2021-07-18T09:53:00.566689Z info Creating operator metrics exporter
2021-07-18T09:53:00.566994Z info Registering Components.
2021-07-18T09:53:00.567636Z info installer Adding controller for IstioOperator.
2021-07-18T09:53:00.568105Z info installer Controller added
2021-07-18T09:53:00.568131Z info Starting the Cmd.
2021-07-18T09:53:00.568734Z info klog attempting to acquire leader lease istio-operator/istio-operator-lock...
2021-07-18T09:53:23.919016Z info klog successfully acquired lease istio-operator/istio-operator-lock
2021-07-18T09:53:23.924778Z info proto: tag has too few fields: "-"
2021-07-18T09:53:23.925446Z error klog k8s.io/client-go@v0.20.5/tools/cache/reflector.go:167: Failed to watch *v1alpha1.IstioOperator: failed to list *v1alpha1.IstioOperator: v1alpha1.IstioOperatorList.Items: []v1alpha1.IstioOperator: v1alpha1.IstioOperator.Status: Spec: unmarshalerDecoder: json: cannot unmarshal object into Go value of type string, error found in #10 byte of ...|h"]}]}]}}},"status":|..., bigger context ...|e","kube-prometheus-stack-admission-patch"]}]}]}}},"status":{"componentStatus":{"Base":{"status":"HE|...
2021-07-18T09:53:25.410070Z error klog k8s.io/client-go@v0.20.5/tools/cache/reflector.go:167: Failed to watch *v1alpha1.IstioOperator: failed to list *v1alpha1.IstioOperator: v1alpha1.IstioOperatorList.Items: []v1alpha1.IstioOperator: v1alpha1.IstioOperator.Status: Spec: unmarshalerDecoder: json: cannot unmarshal object into Go value of type string, error found in #10 byte of ...|h"]}]}]}}},"status":|..., bigger context ...|e","kube-prometheus-stack-admission-patch"]}]}]}}},"status":{"componentStatus":{"Base":{"status":"HE|...
Then everything works flawlessly, the crds are deployed, #169 gets solved but ofc, that creates other issues down the line. Any idea how to solve this? Thanks!
Closing, it was probably something that I changed myself but the definition of istio-operator.yaml doesn't match what is currently on this repo, the is no configmap on this repo. Sorry for that.
When I deploy in my cluster I get this for
istio-operator
:So everything seems fine until I get the pod logs:
and when I get try to get the crds:
No trace of istio crds resulting in this:
It seems the
distribution/istio/istio-spec.yaml
is referencing a config map that is non-existing:I can't find any
cluster-parameters
configmap in the repo.If I comment out this part of
distribution/istio/istio-spec.yaml
:Then everything works flawlessly, the crds are deployed, #169 gets solved but ofc, that creates other issues down the line. Any idea how to solve this? Thanks!