-
Story
-
Resolution: Done
-
Blocker
-
OSSM 2.0.0
-
13
-
False
-
False
-
Undefined
Part 1 - Document how to configure Kiali via the SMCP.
Part 2 - Document the full Kiali config available via the Kaili custom resource (CR)
*******************************************************************************************
Kiali CR reference now published on kiali.io https://kiali.io/docs/configuration/kialis.kiali.io/
Update the Config Reference for Configuring Kiali section for the 2.0 SMCP. Currently the documentation still shows the SMCP configuration from version 1.x.
https://github.com/kiali/kiali-operator/tree/master/deploy/kiali
kiali_cr_minimal.yaml - minimum to create kiali with defaults (4 lines long)
kiali_cr_dev_servicemesh.yml - assume this documents a CR for OSSM (47 lines long)
kiali_cr.yaml fully documents all configuration options (768 lines, but most of that is code comments)
See KIALI-3275 first comment for list of parameters/settings customers should NOT change.
Like Jaeger, you can now configure Kiali outside the SMCP and just reference the Kaili CR.
SMCP does not overwrite Kiali customizations. Need to verify what the supported paths are here to the custom CR.
1 - Configure SMCP -> SMCP creates Kiali CR -> Customer then wants to customize the Kiali CR (SMCP no longer overwrites these customizations)
2 - (Need to confirm if this is supported, this is how it works for External Jaeger) Create custom Kiali CR -> Reference the Kiali CR in the SMCP (similar to external Jaeger CR) -> SMCP uses the custom Kiali CR for install/configuration.
Capturing a Slack conversation here. (8/4/21)
If you install OSSM 2.1 and you install Kiali OUTSIDE of the OSSM operator (i.e. you disable kiali within the SMCP and then manually install Kiali) you need to create a NetworkPolicy. Should look something like:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: kiali
namespace: istio-system
labels:
app.kubernetes.io/name: kiali
spec:
podSelector:
matchLabels:
app.kubernetes.io/name: kiali
policyTypes: ["Ingress"]
ingress: [{}]
this looks required when on OpenShift 4.8
- blocks
-
OSSM-2584 Update topic for accessing Prometheus
- Closed
- is cloned by
-
OSSM-3209 Update the Config Reference - Configuring Kiali topic for 2.0 - Part 2
- Closed
- is related to
-
OSSM-2525 Kiali in getting started workflow
- Closed
- relates to
-
OSSM-2670 Document Kiali configuration
- Closed
-
OSSM-3123 [Kiali] Document setting for read-only Kiali
- Closed
- links to