Hello there,
From Kiali I’d like to read the enableAutoMtls
variable in order to show some mTLS-related information. I am wondering if there is a easy way to retrieve that information without relying in the ConfigMap. Is there any CRD which I can fetch?
I see in the API repo you guys have the MeshConfig, but I don’t know where I have to point and which URI is to fet that information.
// MeshConfig defines mesh-wide variables shared by all Envoy instances in the
// Istio service mesh.
//
// NOTE: This configuration type should be used for the low-level global
// configuration, such as component addresses and port numbers. It should not
// be used for the features of the mesh that can be scoped by service or by
// namespace. Some of the fields in the mesh config are going to be deprecated
// and replaced with several individual configuration types (for example,
// tracing configuration).
message MeshConfig {
// Address of the server that will be used by the proxies for policy
// check calls. By using different names for mixerCheckServer and
// mixerReportServer, it is possible to have one set of Mixer servers handle
// policy check calls while another set of Mixer servers handle telemetry
// calls.
//
// NOTE: Omitting mixerCheckServer while specifying mixerReportServer is
// equivalent to setting disablePolicyChecks to true.
string mixer_check_server = 1;
Thank you in advance,
linsun
January 13, 2020, 3:32pm
2
Hi,
MeshConfig is planned to be avail in the operator CRD, see:
string install_package_path = 11;
// Root for docker image paths e.g. docker.io/istio
string hub = 12;
// Version tag for docker images e.g. 1.0.6
string tag = 13;
// Resource suffix is appended to all resources installed by each component. Used in upgrade scenarios where two
// Istio control planes must exist in the same namespace.
string resource_suffix = 14;
// Config used by control plane components internally.
istio.mesh.v1alpha1.MeshConfig mesh_config = 40;
// Kubernetes resource settings, enablement and component-specific settings that are not internal to the
// component.
IstioComponentSetSpec components = 50;
// Extra addon components which are not explicitly specified above.
map<string, ExternalComponentSpec> addon_components = 51;
// Overrides for default values.yaml. This is a validated pass-through to Helm templates.
// See the Helm installation options for schema details: https://istio.io/docs/reference/config/installation-options/.
Check on #environments group for when it should land… I think it is targeted for 1.5.
Thanks,
Lin