From 06567cfb7d064989f4e1eb08551cfb15d2abc70a Mon Sep 17 00:00:00 2001 From: Linus Vogel Date: Sat, 4 Jul 2026 15:36:16 +0200 Subject: [PATCH] autocommit --- helm/kiali/templates/kiali-cr.yaml | 18 ---- helm/kiali/values.yaml | 128 +---------------------------- 2 files changed, 4 insertions(+), 142 deletions(-) delete mode 100644 helm/kiali/templates/kiali-cr.yaml diff --git a/helm/kiali/templates/kiali-cr.yaml b/helm/kiali/templates/kiali-cr.yaml deleted file mode 100644 index ec66c98..0000000 --- a/helm/kiali/templates/kiali-cr.yaml +++ /dev/null @@ -1,18 +0,0 @@ -apiVersion: kiali.io/v1alpha1 -kind: Kiali -metadata: - name: kiali - namespace: istio-system -spec: - auth: - strategy: anonymous - deployment: - accessible_namespaces: - - '**' - ingress: - enabled: true - external_services: - istio: - root_namespace: istio-system -# prometheus: -# url: http://prometheus.istio-system:9090 diff --git a/helm/kiali/values.yaml b/helm/kiali/values.yaml index c270e44..c9f9b03 100644 --- a/helm/kiali/values.yaml +++ b/helm/kiali/values.yaml @@ -1,126 +1,6 @@ -nameOverride: "" -fullnameOverride: "" - -image: # see: https://quay.io/repository/kiali/kiali-operator?tab=tags - repo: ${HELM_IMAGE_REPO} # quay.io/kiali/kiali-operator - tag: ${HELM_IMAGE_TAG} # version string like v1.39.0 or a digest hash - digest: "" # use "sha256" if tag is a sha256 hash (do NOT prefix this value with a "@") - pullPolicy: Always - pullSecrets: [] - -# Deployment options for the operator pod. -extraLabels: {} -nodeSelector: {} -podAnnotations: {} -podLabels: {} -env: [] -tolerations: [] -resources: - requests: - cpu: "10m" - memory: "64Mi" -affinity: {} -replicaCount: 1 -priorityClassName: "" -securityContext: {} - -# This helm chart will create Kubernetes resources such as cluster roles, cluster role bindings, and service accounts. -# For very rare use-cases, users may want to manage some of these resources manually, outside -# of this helm chart. In cases like this, you can inform this helm chart to skip the creation of -# those resources that you want to manage yourself. -# For example, if you want to manage cluster roles and cluster role bindings yourself, but you still want this helm -# chart to create service accounts, set the value of "skipResources" to an array -# value of ["clusterrole", "clusterrolebinding"]. -# If you use this feature, you must be aware that you then bear the responsibility of -# creating these resources yourself manually; if you do not then the installation -# will be broken. Therefore, only use this feature if you know what you are doing. -# Valid list item values are: "clusterrole", "clusterrolebinding", "sa" -skipResources: [] - -# metrics.enabled: set to true if you want Prometheus to collect metrics from the operator -metrics: - enabled: true - -# debug.enabled: when true the full ansible logs are dumped after each reconciliation run -# debug.verbosity: defines the amount of details the operator will log (higher numbers are more noisy) -# debug.enableProfiler: when true (regardless of debug.enabled), timings for the most expensive tasks will be logged after each reconciliation loop -debug: - enabled: true - verbosity: "1" - enableProfiler: false - -# Defines where the operator will look for Kial CR resources. "" means "all namespaces". -watchNamespace: "" - -# Set to true if you want the operator to be able to create cluster roles. This is necessary -# if you want to support Kiali CRs with spec.deployment.cluster_wide_access=true. -# Setting this to "true" requires allowAllAccessibleNamespaces to be "true" also. -# Note that this will be overriden to "true" if cr.create is true and cr.spec.deployment.cluster_wide_access=true. -clusterRoleCreator: true - -# Set to true if you want to allow the operator to only be able to install Kiali in view-only-mode. -# The purpose for this setting is to allow you to restrict the permissions given to the operator itself. -onlyViewOnlyMode: false - -# allowAdHocKialiNamespace tells the operator to allow a user to be able to install a Kiali CR in one namespace but -# be able to install Kiali in another namespace. In other words, it will allow the Kiali CR spec.deployment.namespace -# to be something other than the namespace where the CR is installed. You may want to disable this if you are -# running in a multi-tenant scenario in which you only want a user to be able to install Kiali in the same namespace -# where the user has permissions to install a Kiali CR. -allowAdHocKialiNamespace: true - -# allowAdHocKialiImage tells the operator to allow a user to be able to install a custom Kiali image as opposed -# to the image the operator will install by default. In other words, it will allow the -# Kiali CR spec.deployment.image_name and spec.deployment.image_version to be configured by the user. -# You may want to disable this if you do not want users to install their own Kiali images. -allowAdHocKialiImage: false - -# allowAdHocOSSMConsoleImage tells the operator to allow a user to be able to install a custom OSSMC image as opposed -# to the image the operator will install by default. In other words, it will allow the -# OSSMConsole CR spec.deployment.imageName and spec.deployment.imageVersion to be configured by the user. -# You may want to disable this if you do not want users to install their own OSSMC images. -# This is only applicable when running on OpenShift. -allowAdHocOSSMConsoleImage: false - -# allowAdHocContainers tells the operator to allow a user to be able to install additional pod containers and initContainers to the Kiali pod. -# In other words, it will allow the Kiali CR spec.deployment.additional_pod_containers_yaml and -# spec.deployment.additional_pod_init_containers_yaml to be configured by the user. -# The operator will apply a restrictive security context to user-defined containers and will prevent -# write access to secret-backed volumes. These restrictions cannot be overridden. -allowAdHocContainers: false - -# allowSecurityContextOverride tells the operator to allow a user to be able to fully override the Kiali -# container securityContext. If this is false, certain securityContext settings must exist on the Kiali -# container and any attempt to override them will be ignored. -allowSecurityContextOverride: false - -# allowAllAccessibleNamespaces tells the operator to allow a user to be able to configure Kiali -# to access all namespaces in the cluster via spec.deployment.cluster_wide_access=true. -# If this is false, the user must specify an explicit set of namespaces in the Kiali CR via spec.deployment.discovery_selectors. -# Setting this to "true" requires clusterRoleCreator to be "true" also. -# Note that this will be overriden to "true" if cr.create is true and cr.spec.deployment.cluster_wide_access=true. -allowAllAccessibleNamespaces: true - -# watchesFile: If specified, this determines what watches file will be used to configure the operator. There are four different -# files that can be selected: (a) `watches-os.yaml`, (b) `watches-os-ns.yaml`, (c) `watches-k8s.yaml` or (d) `watches-k8s-ns.yaml`. -# The first two are for OpenShift only, the last two are for non-OpenShift Kubernetes clusters. The two with "-ns" in their name -# enable the operator to automatically update the Kiali Server with access to new namespaces as those namespaces are created in -# the cluster. This namespace watching feature provides some advanced capabilities but is never required. It is also not -# the default behavior and is not necessary if your Kiali CRs will have `spec.deployment.cluster_wide_access` set to `true`. -watchesFile: "" - -# For what a Kiali CR spec can look like, see: https://kiali.io/docs/configuration/kialis.kiali.io/ cr: - create: false - name: kiali - # If you elect to create a Kiali CR (--set cr.create=true) - # and the operator is watching all namespaces (--set watchNamespace="") - # then this is the namespace where the CR will be created (the default will be the operator namespace). - namespace: "" - - # Annotations to place in the Kiali CR metadata. - annotations: {} - + create: true + namespace: istio-system spec: - deployment: - cluster_wide_access: true \ No newline at end of file + auth: + strategy: anonymous \ No newline at end of file