当前位置: 首页 > news >正文

自适应网站建设方案/知乎seo优化

自适应网站建设方案,知乎seo优化,网站建设 外包,wix网站建设目录 一、Helm安装 二、安装mysql 1、拉取镜像 2、修改配置文件 3、创建mysql-secret 4、安装 一、Helm安装 这里不再赘叙,具体安装请参考官网 Helm | 快速入门指南 二、安装mysql 1、拉取镜像 #添加仓库 helm repo add bitnami https://charts.bitnami.c…

目录

一、Helm安装

二、安装mysql

1、拉取镜像

2、修改配置文件

3、创建mysql-secret

4、安装


一、Helm安装

这里不再赘叙,具体安装请参考官网

Helm | 快速入门指南

二、安装mysql

1、拉取镜像

#添加仓库
helm repo add bitnami https://charts.bitnami.com/bitnami#搜索镜像
helm search repo mysql#拉取镜像
helm pull bitnami/mysql --version  12.0.0#加压文件
tar -zxf mysql-12.0.0.tgz

2、修改配置文件

# Copyright Broadcom, Inc. All Rights Reserved.
# SPDX-License-Identifier: APACHE-2.0## @section Global parameters
## Global Docker image parameters
## Please, note that this will override the image parameters, including dependencies, configured to use the global value
## Current available global Docker image parameters: imageRegistry, imagePullSecrets and storageClass
#### @param global.imageRegistry Global Docker image registry
## @param global.imagePullSecrets Global Docker registry secret names as an array
## @param global.defaultStorageClass Global default StorageClass for Persistent Volume(s)
## @param global.storageClass DEPRECATED: use global.defaultStorageClass instead
##
global:imageRegistry: ""## E.g.## imagePullSecrets:##   - myRegistryKeySecretName##imagePullSecrets: []defaultStorageClass: "manager-nfs-storage"  #修改这里为自己的scstorageClass: ""## Compatibility adaptations for Kubernetes platforms##compatibility:## Compatibility adaptations for Openshift##openshift:## @param global.compatibility.openshift.adaptSecurityContext Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation)##adaptSecurityContext: auto
## @section Common parameters
#### @param kubeVersion Force target Kubernetes version (using Helm capabilities if not set)
##
kubeVersion: ""
## @param nameOverride String to partially override common.names.fullname template (will maintain the release name)
##
nameOverride: ""
## @param fullnameOverride String to fully override common.names.fullname template
##
fullnameOverride: ""
## @param namespaceOverride String to fully override common.names.namespace
##
namespaceOverride: ""
## @param clusterDomain Cluster domain
##
clusterDomain: cluster.local
## @param commonAnnotations Common annotations to add to all MySQL resources (sub-charts are not considered). Evaluated as a template
##
commonAnnotations: {}
## @param commonLabels Common labels to add to all MySQL resources (sub-charts are not considered). Evaluated as a template
##
commonLabels: {}
## @param extraDeploy Array with extra yaml to deploy with the chart. Evaluated as a template
##
extraDeploy: []
## @param serviceBindings.enabled Create secret for service binding (Experimental)
## Ref: https://servicebinding.io/service-provider/
##
serviceBindings:enabled: false
## Enable diagnostic mode in the deployment
##
diagnosticMode:## @param diagnosticMode.enabled Enable diagnostic mode (all probes will be disabled and the command will be overridden)##enabled: false## @param diagnosticMode.command Command to override all containers in the deployment##command:- sleep## @param diagnosticMode.args Args to override all containers in the deployment##args:- infinity
## @section MySQL common parameters
#### Bitnami MySQL image
## ref: https://hub.docker.com/r/bitnami/mysql/tags/
## @param image.registry [default: REGISTRY_NAME] MySQL image registry
## @param image.repository [default: REPOSITORY_NAME/mysql] MySQL image repository
## @skip image.tag MySQL image tag (immutable tags are recommended)
## @param image.digest MySQL image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
## @param image.pullPolicy MySQL image pull policy
## @param image.pullSecrets Specify docker-registry secret names as an array
## @param image.debug Specify if debug logs should be enabled
##
image:registry: docker.iorepository: bitnami/mysqltag: 8.4.3-debian-12-r0digest: ""## Specify a imagePullPolicy## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images##pullPolicy: IfNotPresent## Optionally specify an array of imagePullSecrets (secrets must be manually created in the namespace)## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/## Example:## pullSecrets:##   - myRegistryKeySecretName##pullSecrets: []## Set to true if you would like to see extra information on logs## It turns BASH and/or NAMI debugging in the image##debug: false
## @param architecture MySQL architecture (`standalone` or `replication`)
##
architecture: replication  #这里指定replication
## MySQL Authentication parameters
##
auth:## @param auth.rootPassword Password for the `root` user. Ignored if existing secret is provided## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#setting-the-root-password-on-first-run##rootPassword: ""## @param auth.createDatabase Whether to create the .Values.auth.database or not## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-on-first-run##createDatabase: true## @param auth.database Name for a custom database to create## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-on-first-run##database: "my_database"## @param auth.username Name for a custom user to create## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#creating-a-database-user-on-first-run##username: ""## @param auth.password Password for the new user. Ignored if existing secret is provided##password: ""## @param auth.replicationUser MySQL replication user## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#setting-up-a-replication-cluster##replicationUser: replicator## @param auth.replicationPassword MySQL replication user password. Ignored if existing secret is provided##replicationPassword: ""## @param auth.existingSecret Use existing secret for password details. The secret has to contain the keys `mysql-root-password`, `mysql-replication-password` and `mysql-password`## NOTE: When it's set the auth.rootPassword, auth.password, auth.replicationPassword are ignored.##existingSecret: "mysql-secret"   #这里修改为自己创建的secret,如果不修改这里,就指定上面的rootPassword属性## @param auth.usePasswordFiles Mount credentials as files instead of using an environment variable##usePasswordFiles: false## @param auth.customPasswordFiles Use custom password files when `auth.usePasswordFiles` is set to `true`. Define path for keys `root` and `user`, also define `replicator` if `architecture` is set to `replication`## Example:## customPasswordFiles:##   root: /vault/secrets/mysql-root##   user: /vault/secrets/mysql-user##   replicator: /vault/secrets/mysql-replicator##customPasswordFiles: {}## @param auth.authenticationPolicy Sets the authentication policy, by default it will use `* ,,`## ref: https://dev.mysql.com/doc/refman/8.4/en/server-system-variables.html#sysvar_authentication_policy##authenticationPolicy: ""
## @param initdbScripts Dictionary of initdb scripts
## Specify dictionary of scripts to be run at first boot
## Example:
## initdbScripts:
##   my_init_script.sh: |
##      #!/bin/bash
##      echo "Do something."
##
initdbScripts: {}
## @param initdbScriptsConfigMap ConfigMap with the initdb scripts (Note: Overrides `initdbScripts`)
##
initdbScriptsConfigMap: ""
## @param startdbScripts Dictionary of startdb scripts
## Specify dictionary of scripts to be run every time the container is started
## Example:
## startdbScripts:
##   my_start_script.sh: |
##      #!/bin/bash
##      echo "Do something."
##
startdbScripts: {}
## @param startdbScriptsConfigMap ConfigMap with the startdb scripts (Note: Overrides `startdbScripts`)
##
startdbScriptsConfigMap: ""
## @section MySQL Primary parameters
##
primary:## @param primary.name Name of the primary database (eg primary, master, leader, ...)##name: master## @param primary.command Override default container command on MySQL Primary container(s) (useful when using custom images)##command: []## @param primary.args Override default container args on MySQL Primary container(s) (useful when using custom images)##args: []## @param primary.lifecycleHooks for the MySQL Primary container(s) to automate configuration before or after startup##lifecycleHooks: {}## @param primary.automountServiceAccountToken Mount Service Account token in pod##automountServiceAccountToken: false## @param primary.hostAliases Deployment pod host aliases## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/##hostAliases: []## @param primary.enableMySQLX Enable mysqlx port## ref: https://dev.mysql.com/doc/dev/mysql-server/latest/mysqlx_protocol_xplugin.html##enableMySQLX: false## @param primary.configuration [string] Configure MySQL Primary with a custom my.cnf file## ref: https://mysql.com/kb/en/mysql/configuring-mysql-with-mycnf/#example-of-configuration-file##configuration: |-[mysqld]authentication_policy='{{- .Values.auth.authenticationPolicy | default "* ,," }}'skip-name-resolveexplicit_defaults_for_timestampbasedir=/opt/bitnami/mysqlplugin_dir=/opt/bitnami/mysql/lib/pluginport={{ .Values.primary.containerPorts.mysql }}mysqlx={{ ternary 1 0 .Values.primary.enableMySQLX }}mysqlx_port={{ .Values.primary.containerPorts.mysqlx }}socket=/opt/bitnami/mysql/tmp/mysql.sockdatadir=/bitnami/mysql/datatmpdir=/opt/bitnami/mysql/tmpmax_allowed_packet=16Mbind-address=*pid-file=/opt/bitnami/mysql/tmp/mysqld.pidlog-error=/opt/bitnami/mysql/logs/mysqld.logcharacter-set-server=UTF8slow_query_log=0long_query_time=10.0[client]port={{ .Values.primary.containerPorts.mysql }}socket=/opt/bitnami/mysql/tmp/mysql.sockdefault-character-set=UTF8plugin_dir=/opt/bitnami/mysql/lib/plugin[manager]port={{ .Values.primary.containerPorts.mysql }}socket=/opt/bitnami/mysql/tmp/mysql.sockpid-file=/opt/bitnami/mysql/tmp/mysqld.pid## @param primary.existingConfigmap Name of existing ConfigMap with MySQL Primary configuration.## NOTE: When it's set the 'configuration' parameter is ignored##existingConfigmap: ""## @param primary.containerPorts.mysql Container port for mysql## @param primary.containerPorts.mysqlx Container port for mysqlx##containerPorts:mysql: 3306mysqlx: 33060## @param primary.updateStrategy.type Update strategy type for the MySQL primary statefulset## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies##updateStrategy:type: RollingUpdate## @param primary.podAnnotations Additional pod annotations for MySQL primary pods## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/##podAnnotations: {}## @param primary.podAffinityPreset MySQL primary pod affinity preset. Ignored if `primary.affinity` is set. Allowed values: `soft` or `hard`## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity##podAffinityPreset: ""## @param primary.podAntiAffinityPreset MySQL primary pod anti-affinity preset. Ignored if `primary.affinity` is set. Allowed values: `soft` or `hard`## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity##podAntiAffinityPreset: soft## MySQL Primary node affinity preset## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity##nodeAffinityPreset:## @param primary.nodeAffinityPreset.type MySQL primary node affinity preset type. Ignored if `primary.affinity` is set. Allowed values: `soft` or `hard`##type: ""## @param primary.nodeAffinityPreset.key MySQL primary node label key to match Ignored if `primary.affinity` is set.## E.g.## key: "kubernetes.io/e2e-az-name"##key: ""## @param primary.nodeAffinityPreset.values MySQL primary node label values to match. Ignored if `primary.affinity` is set.## E.g.## values:##   - e2e-az1##   - e2e-az2##values: []## @param primary.affinity Affinity for MySQL primary pods assignment## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity## Note: podAffinityPreset, podAntiAffinityPreset, and  nodeAffinityPreset will be ignored when it's set##affinity: {}## @param primary.nodeSelector Node labels for MySQL primary pods assignment## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/##nodeSelector: {}## @param primary.tolerations Tolerations for MySQL primary pods assignment## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/##tolerations: []## @param primary.priorityClassName MySQL primary pods' priorityClassName##priorityClassName: ""## @param primary.runtimeClassName MySQL primary pods' runtimeClassName##runtimeClassName: ""## @param primary.schedulerName Name of the k8s scheduler (other than default)## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/##schedulerName: ""## @param primary.terminationGracePeriodSeconds In seconds, time the given to the MySQL primary pod needs to terminate gracefully## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods##terminationGracePeriodSeconds: ""## @param primary.topologySpreadConstraints Topology Spread Constraints for pod assignment## https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/## The value is evaluated as a template##topologySpreadConstraints: []## @param primary.podManagementPolicy podManagementPolicy to manage scaling operation of MySQL primary pods## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies##podManagementPolicy: ""## MySQL primary Pod security context## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod## @param primary.podSecurityContext.enabled Enable security context for MySQL primary pods## @param primary.podSecurityContext.fsGroupChangePolicy Set filesystem group change policy## @param primary.podSecurityContext.sysctls Set kernel settings using the sysctl interface## @param primary.podSecurityContext.supplementalGroups Set filesystem extra groups## @param primary.podSecurityContext.fsGroup Group ID for the mounted volumes' filesystem##podSecurityContext:enabled: truefsGroupChangePolicy: Alwayssysctls: []supplementalGroups: []fsGroup: 1001## MySQL primary container security context## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container## @param primary.containerSecurityContext.enabled MySQL primary container securityContext## @param primary.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container## @param primary.containerSecurityContext.runAsUser User ID for the MySQL primary container## @param primary.containerSecurityContext.runAsGroup Group ID for the MySQL primary container## @param primary.containerSecurityContext.runAsNonRoot Set MySQL primary container's Security Context runAsNonRoot## @param primary.containerSecurityContext.allowPrivilegeEscalation Set container's privilege escalation## @param primary.containerSecurityContext.capabilities.drop Set container's Security Context runAsNonRoot## @param primary.containerSecurityContext.seccompProfile.type Set Client container's Security Context seccomp profile## @param primary.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem##containerSecurityContext:enabled: trueseLinuxOptions: {}runAsUser: 1001runAsGroup: 1001runAsNonRoot: trueallowPrivilegeEscalation: falsecapabilities:drop: ["ALL"]seccompProfile:type: "RuntimeDefault"readOnlyRootFilesystem: true## MySQL primary container's resource requests and limits## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/## We usually recommend not to specify default resources and to leave this as a conscious## choice for the user. This also increases chances charts run on environments with little## resources, such as Minikube. If you do want to specify resources, uncomment the following## lines, adjust them as necessary, and remove the curly braces after 'resources:'.## @param primary.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if primary.resources is set (primary.resources is recommended for production).## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15##resourcesPreset: "small"## @param primary.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)## Example:## resources:##   requests:##     cpu: 2##     memory: 512Mi##   limits:##     cpu: 3##     memory: 1024Mi##resources: {}## Configure extra options for liveness probe## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes## @param primary.livenessProbe.enabled Enable livenessProbe## @param primary.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe## @param primary.livenessProbe.periodSeconds Period seconds for livenessProbe## @param primary.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe## @param primary.livenessProbe.failureThreshold Failure threshold for livenessProbe## @param primary.livenessProbe.successThreshold Success threshold for livenessProbe##livenessProbe:enabled: trueinitialDelaySeconds: 5periodSeconds: 10timeoutSeconds: 1failureThreshold: 3successThreshold: 1## Configure extra options for readiness probe## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes## @param primary.readinessProbe.enabled Enable readinessProbe## @param primary.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe## @param primary.readinessProbe.periodSeconds Period seconds for readinessProbe## @param primary.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe## @param primary.readinessProbe.failureThreshold Failure threshold for readinessProbe## @param primary.readinessProbe.successThreshold Success threshold for readinessProbe##readinessProbe:enabled: trueinitialDelaySeconds: 5periodSeconds: 10timeoutSeconds: 1failureThreshold: 3successThreshold: 1## Configure extra options for startupProbe probe## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes## @param primary.startupProbe.enabled Enable startupProbe## @param primary.startupProbe.initialDelaySeconds Initial delay seconds for startupProbe## @param primary.startupProbe.periodSeconds Period seconds for startupProbe## @param primary.startupProbe.timeoutSeconds Timeout seconds for startupProbe## @param primary.startupProbe.failureThreshold Failure threshold for startupProbe## @param primary.startupProbe.successThreshold Success threshold for startupProbe##startupProbe:enabled: trueinitialDelaySeconds: 15periodSeconds: 10timeoutSeconds: 1failureThreshold: 10successThreshold: 1## @param primary.customLivenessProbe Override default liveness probe for MySQL primary containers##customLivenessProbe: {}## @param primary.customReadinessProbe Override default readiness probe for MySQL primary containers##customReadinessProbe: {}## @param primary.customStartupProbe Override default startup probe for MySQL primary containers##customStartupProbe: {}## @param primary.extraFlags MySQL primary additional command line flags## Can be used to specify command line flags, for example:## E.g.## extraFlags: "--max-connect-errors=1000 --max_connections=155"##extraFlags: ""## @param primary.extraEnvVars Extra environment variables to be set on MySQL primary containers## E.g.## extraEnvVars:##  - name: TZ##    value: "Europe/Paris"##extraEnvVars: []## @param primary.extraEnvVarsCM Name of existing ConfigMap containing extra env vars for MySQL primary containers##extraEnvVarsCM: ""## @param primary.extraEnvVarsSecret Name of existing Secret containing extra env vars for MySQL primary containers##extraEnvVarsSecret: ""## @param primary.extraPodSpec Optionally specify extra PodSpec for the MySQL Primary pod(s)##extraPodSpec: {}## @param primary.extraPorts Extra ports to expose##extraPorts: []## Enable persistence using Persistent Volume Claims## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/##persistence:## @param primary.persistence.enabled Enable persistence on MySQL primary replicas using a `PersistentVolumeClaim`. If false, use emptyDir##enabled: true## @param primary.persistence.existingClaim Name of an existing `PersistentVolumeClaim` for MySQL primary replicas## NOTE: When it's set the rest of persistence parameters are ignored##existingClaim: ""## @param primary.persistence.subPath The name of a volume's sub path to mount for persistence##subPath: ""## @param primary.persistence.storageClass MySQL primary persistent volume storage Class## If defined, storageClassName: <storageClass>## If set to "-", storageClassName: "", which disables dynamic provisioning## If undefined (the default) or set to null, no storageClassName spec is##   set, choosing the default provisioner.  (gp2 on AWS, standard on##   GKE, AWS & OpenStack)##storageClass: "manager-nfs-storage"   #这里修改自己的sc## @param primary.persistence.annotations MySQL primary persistent volume claim annotations##annotations: {}## @param primary.persistence.accessModes MySQL primary persistent volume access Modes##accessModes:- ReadWriteOnce## @param primary.persistence.size MySQL primary persistent volume size##size: 1Gi   #根据实际情况调整大小## @param primary.persistence.selector Selector to match an existing Persistent Volume## selector:##   matchLabels:##     app: my-app##selector: {}## Primary Persistent Volume Claim Retention Policy## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention##persistentVolumeClaimRetentionPolicy:## @param primary.persistentVolumeClaimRetentionPolicy.enabled Enable Persistent volume retention policy for Primary StatefulSet##enabled: false## @param primary.persistentVolumeClaimRetentionPolicy.whenScaled Volume retention behavior when the replica count of the StatefulSet is reduced##whenScaled: Retain## @param primary.persistentVolumeClaimRetentionPolicy.whenDeleted Volume retention behavior that applies when the StatefulSet is deleted##whenDeleted: Retain## @param primary.extraVolumes Optionally specify extra list of additional volumes to the MySQL Primary pod(s)##extraVolumes: []## @param primary.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the MySQL Primary container(s)##extraVolumeMounts: []## @param primary.initContainers Add additional init containers for the MySQL Primary pod(s)##initContainers: []## @param primary.sidecars Add additional sidecar containers for the MySQL Primary pod(s)##sidecars: []## MySQL Primary Service parameters##service:## @param primary.service.type MySQL Primary K8s service type##type: NodePort    #修改为nodeport,方便外部访问## @param primary.service.ports.mysql MySQL Primary K8s service port## @param primary.service.ports.mysqlx MySQL Primary K8s service mysqlx port##ports:mysql: 3306mysqlx: 33060## @param primary.service.nodePorts.mysql MySQL Primary K8s service node port## @param primary.service.nodePorts.mysqlx MySQL Primary K8s service node port mysqlx## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport##nodePorts:mysql: ""mysqlx: ""## @param primary.service.clusterIP MySQL Primary K8s service clusterIP IP## e.g:## clusterIP: None##clusterIP: ""## @param primary.service.loadBalancerIP MySQL Primary loadBalancerIP if service type is `LoadBalancer`## Set the LoadBalancer service type to internal only## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer##loadBalancerIP: ""## @param primary.service.externalTrafficPolicy Enable client source IP preservation## ref https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip##externalTrafficPolicy: Cluster## @param primary.service.loadBalancerSourceRanges Addresses that are allowed when MySQL Primary service is LoadBalancer## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service## E.g.## loadBalancerSourceRanges:##   - 10.10.10.0/24##loadBalancerSourceRanges: []## @param primary.service.extraPorts Extra ports to expose (normally used with the `sidecar` value)##extraPorts: []## @param primary.service.annotations Additional custom annotations for MySQL primary service##annotations: {}## @param primary.service.sessionAffinity Session Affinity for Kubernetes service, can be "None" or "ClientIP"## If "ClientIP", consecutive client requests will be directed to the same Pod## ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies##sessionAffinity: None## @param primary.service.sessionAffinityConfig Additional settings for the sessionAffinity## sessionAffinityConfig:##   clientIP:##     timeoutSeconds: 300##sessionAffinityConfig: {}## Headless service properties##headless:## @param primary.service.headless.annotations Additional custom annotations for headless MySQL primary service.##annotations: {}## MySQL primary Pod Disruption Budget configuration## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/##pdb:## @param primary.pdb.create Enable/disable a Pod Disruption Budget creation for MySQL primary pods##create: true## @param primary.pdb.minAvailable Minimum number/percentage of MySQL primary pods that should remain scheduled##minAvailable: ""## @param primary.pdb.maxUnavailable Maximum number/percentage of MySQL primary pods that may be made unavailable. Defaults to `1` if both `primary.pdb.minAvailable` and `primary.pdb.maxUnavailable` are empty.##maxUnavailable: ""## @param primary.podLabels MySQL Primary pod label. If labels are same as commonLabels , this will take precedence##podLabels: {}
## @section MySQL Secondary parameters
##
secondary:## @param secondary.name Name of the secondary database (eg secondary, slave, ...)##name: slave   #指定name## @param secondary.replicaCount Number of MySQL secondary replicas##replicaCount: 1   #副本数量## @param secondary.automountServiceAccountToken Mount Service Account token in pod##automountServiceAccountToken: false## @param secondary.hostAliases Deployment pod host aliases## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/##hostAliases: []## @param secondary.command Override default container command on MySQL Secondary container(s) (useful when using custom images)##command: []## @param secondary.args Override default container args on MySQL Secondary container(s) (useful when using custom images)##args: []## @param secondary.lifecycleHooks for the MySQL Secondary container(s) to automate configuration before or after startup##lifecycleHooks: {}## @param secondary.enableMySQLX Enable mysqlx port## ref: https://dev.mysql.com/doc/dev/mysql-server/latest/mysqlx_protocol_xplugin.html##enableMySQLX: false## @param secondary.configuration [string] Configure MySQL Secondary with a custom my.cnf file## ref: https://mysql.com/kb/en/mysql/configuring-mysql-with-mycnf/#example-of-configuration-file##configuration: |-[mysqld]authentication_policy='{{- .Values.auth.authenticationPolicy | default "* ,," }}'skip-name-resolveexplicit_defaults_for_timestampbasedir=/opt/bitnami/mysqlplugin_dir=/opt/bitnami/mysql/lib/pluginport={{ .Values.secondary.containerPorts.mysql }}mysqlx={{ ternary 1 0 .Values.secondary.enableMySQLX }}mysqlx_port={{ .Values.secondary.containerPorts.mysqlx }}socket=/opt/bitnami/mysql/tmp/mysql.sockdatadir=/bitnami/mysql/datatmpdir=/opt/bitnami/mysql/tmpmax_allowed_packet=16Mbind-address=*pid-file=/opt/bitnami/mysql/tmp/mysqld.pidlog-error=/opt/bitnami/mysql/logs/mysqld.logcharacter-set-server=UTF8slow_query_log=0long_query_time=10.0[client]port={{ .Values.secondary.containerPorts.mysql }}socket=/opt/bitnami/mysql/tmp/mysql.sockdefault-character-set=UTF8plugin_dir=/opt/bitnami/mysql/lib/plugin[manager]port={{ .Values.secondary.containerPorts.mysql }}socket=/opt/bitnami/mysql/tmp/mysql.sockpid-file=/opt/bitnami/mysql/tmp/mysqld.pid## @param secondary.existingConfigmap Name of existing ConfigMap with MySQL Secondary configuration.## NOTE: When it's set the 'configuration' parameter is ignored##existingConfigmap: ""## @param secondary.containerPorts.mysql Container port for mysql## @param secondary.containerPorts.mysqlx Container port for mysqlx##containerPorts:mysql: 3306mysqlx: 33060## @param secondary.updateStrategy.type Update strategy type for the MySQL secondary statefulset## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies##updateStrategy:type: RollingUpdate## @param secondary.podAnnotations Additional pod annotations for MySQL secondary pods## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/##podAnnotations: {}## @param secondary.podAffinityPreset MySQL secondary pod affinity preset. Ignored if `secondary.affinity` is set. Allowed values: `soft` or `hard`## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity##podAffinityPreset: ""## @param secondary.podAntiAffinityPreset MySQL secondary pod anti-affinity preset. Ignored if `secondary.affinity` is set. Allowed values: `soft` or `hard`## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity## Allowed values: soft, hard##podAntiAffinityPreset: soft## MySQL Secondary node affinity preset## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity##nodeAffinityPreset:## @param secondary.nodeAffinityPreset.type MySQL secondary node affinity preset type. Ignored if `secondary.affinity` is set. Allowed values: `soft` or `hard`##type: ""## @param secondary.nodeAffinityPreset.key MySQL secondary node label key to match Ignored if `secondary.affinity` is set.## E.g.## key: "kubernetes.io/e2e-az-name"##key: ""## @param secondary.nodeAffinityPreset.values MySQL secondary node label values to match. Ignored if `secondary.affinity` is set.## E.g.## values:##   - e2e-az1##   - e2e-az2##values: []## @param secondary.affinity Affinity for MySQL secondary pods assignment## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity## Note: podAffinityPreset, podAntiAffinityPreset, and  nodeAffinityPreset will be ignored when it's set##affinity: {}## @param secondary.nodeSelector Node labels for MySQL secondary pods assignment## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/##nodeSelector: {}## @param secondary.tolerations Tolerations for MySQL secondary pods assignment## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/##tolerations: []## @param secondary.priorityClassName MySQL secondary pods' priorityClassName##priorityClassName: ""## @param secondary.runtimeClassName MySQL secondary pods' runtimeClassName##runtimeClassName: ""## @param secondary.schedulerName Name of the k8s scheduler (other than default)## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/##schedulerName: ""## @param secondary.terminationGracePeriodSeconds In seconds, time the given to the MySQL secondary pod needs to terminate gracefully## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods##terminationGracePeriodSeconds: ""## @param secondary.topologySpreadConstraints Topology Spread Constraints for pod assignment## https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/## The value is evaluated as a template##topologySpreadConstraints: []## @param secondary.podManagementPolicy podManagementPolicy to manage scaling operation of MySQL secondary pods## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies##podManagementPolicy: ""## MySQL secondary Pod security context## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod## @param secondary.podSecurityContext.enabled Enable security context for MySQL secondary pods## @param secondary.podSecurityContext.fsGroupChangePolicy Set filesystem group change policy## @param secondary.podSecurityContext.sysctls Set kernel settings using the sysctl interface## @param secondary.podSecurityContext.supplementalGroups Set filesystem extra groups## @param secondary.podSecurityContext.fsGroup Group ID for the mounted volumes' filesystem##podSecurityContext:enabled: truefsGroupChangePolicy: Alwayssysctls: []supplementalGroups: []fsGroup: 1001## MySQL secondary container security context## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container## @param secondary.containerSecurityContext.enabled MySQL secondary container securityContext## @param secondary.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container## @param secondary.containerSecurityContext.runAsUser User ID for the MySQL secondary container## @param secondary.containerSecurityContext.runAsGroup Group ID for the MySQL secondary container## @param secondary.containerSecurityContext.runAsNonRoot Set MySQL secondary container's Security Context runAsNonRoot## @param secondary.containerSecurityContext.allowPrivilegeEscalation Set container's privilege escalation## @param secondary.containerSecurityContext.capabilities.drop Set container's Security Context runAsNonRoot## @param secondary.containerSecurityContext.seccompProfile.type Set container's Security Context seccomp profile## @param secondary.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem##containerSecurityContext:enabled: trueseLinuxOptions: {}runAsUser: 1001runAsGroup: 1001runAsNonRoot: trueallowPrivilegeEscalation: falsecapabilities:drop: ["ALL"]seccompProfile:type: "RuntimeDefault"readOnlyRootFilesystem: true## MySQL secondary container's resource requests and limits## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/## We usually recommend not to specify default resources and to leave this as a conscious## choice for the user. This also increases chances charts run on environments with little## resources, such as Minikube. If you do want to specify resources, uncomment the following## lines, adjust them as necessary, and remove the curly braces after 'resources:'.## @param secondary.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if secondary.resources is set (secondary.resources is recommended for production).## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15##resourcesPreset: "small"## @param secondary.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)## Example:## resources:##   requests:##     cpu: 2##     memory: 512Mi##   limits:##     cpu: 3##     memory: 1024Mi##resources: {}## Configure extra options for liveness probe## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes## @param secondary.livenessProbe.enabled Enable livenessProbe## @param secondary.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe## @param secondary.livenessProbe.periodSeconds Period seconds for livenessProbe## @param secondary.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe## @param secondary.livenessProbe.failureThreshold Failure threshold for livenessProbe## @param secondary.livenessProbe.successThreshold Success threshold for livenessProbe##livenessProbe:enabled: trueinitialDelaySeconds: 5periodSeconds: 10timeoutSeconds: 1failureThreshold: 3successThreshold: 1## Configure extra options for readiness probe## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes## @param secondary.readinessProbe.enabled Enable readinessProbe## @param secondary.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe## @param secondary.readinessProbe.periodSeconds Period seconds for readinessProbe## @param secondary.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe## @param secondary.readinessProbe.failureThreshold Failure threshold for readinessProbe## @param secondary.readinessProbe.successThreshold Success threshold for readinessProbe##readinessProbe:enabled: trueinitialDelaySeconds: 5periodSeconds: 10timeoutSeconds: 1failureThreshold: 3successThreshold: 1## Configure extra options for startupProbe probe## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes## @param secondary.startupProbe.enabled Enable startupProbe## @param secondary.startupProbe.initialDelaySeconds Initial delay seconds for startupProbe## @param secondary.startupProbe.periodSeconds Period seconds for startupProbe## @param secondary.startupProbe.timeoutSeconds Timeout seconds for startupProbe## @param secondary.startupProbe.failureThreshold Failure threshold for startupProbe## @param secondary.startupProbe.successThreshold Success threshold for startupProbe##startupProbe:enabled: trueinitialDelaySeconds: 15periodSeconds: 10timeoutSeconds: 1failureThreshold: 15successThreshold: 1## @param secondary.customLivenessProbe Override default liveness probe for MySQL secondary containers##customLivenessProbe: {}## @param secondary.customReadinessProbe Override default readiness probe for MySQL secondary containers##customReadinessProbe: {}## @param secondary.customStartupProbe Override default startup probe for MySQL secondary containers##customStartupProbe: {}## @param secondary.extraFlags MySQL secondary additional command line flags## Can be used to specify command line flags, for example:## E.g.## extraFlags: "--max-connect-errors=1000 --max_connections=155"##extraFlags: ""## @param secondary.extraEnvVars An array to add extra environment variables on MySQL secondary containers## E.g.## extraEnvVars:##  - name: TZ##    value: "Europe/Paris"##extraEnvVars: []## @param secondary.extraEnvVarsCM Name of existing ConfigMap containing extra env vars for MySQL secondary containers##extraEnvVarsCM: ""## @param secondary.extraEnvVarsSecret Name of existing Secret containing extra env vars for MySQL secondary containers##extraEnvVarsSecret: ""## @param secondary.extraPodSpec Optionally specify extra PodSpec for the MySQL Secondary pod(s)##extraPodSpec: {}## @param secondary.extraPorts Extra ports to expose##extraPorts: []## Enable persistence using Persistent Volume Claims## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/##persistence:## @param secondary.persistence.enabled Enable persistence on MySQL secondary replicas using a `PersistentVolumeClaim`##enabled: true## @param secondary.persistence.existingClaim Name of an existing `PersistentVolumeClaim` for MySQL secondary replicas## NOTE: When it's set the rest of persistence parameters are ignored##existingClaim: ""## @param secondary.persistence.subPath The name of a volume's sub path to mount for persistence##subPath: ""## @param secondary.persistence.storageClass MySQL secondary persistent volume storage Class## If defined, storageClassName: <storageClass>## If set to "-", storageClassName: "", which disables dynamic provisioning## If undefined (the default) or set to null, no storageClassName spec is##   set, choosing the default provisioner.  (gp2 on AWS, standard on##   GKE, AWS & OpenStack)##storageClass: "manager-nfs-storage"   #修改为自己的sc## @param secondary.persistence.annotations MySQL secondary persistent volume claim annotations##annotations: {}## @param secondary.persistence.accessModes MySQL secondary persistent volume access Modes##accessModes:- ReadWriteOnce## @param secondary.persistence.size MySQL secondary persistent volume size##size: 1Gi  #根据实际情况修改,我这里做测试,写的比较小## @param secondary.persistence.selector Selector to match an existing Persistent Volume## selector:##   matchLabels:##     app: my-app##selector: {}## Secondary Persistent Volume Claim Retention Policy## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention##persistentVolumeClaimRetentionPolicy:## @param secondary.persistentVolumeClaimRetentionPolicy.enabled Enable Persistent volume retention policy for read only StatefulSet##enabled: false## @param secondary.persistentVolumeClaimRetentionPolicy.whenScaled Volume retention behavior when the replica count of the StatefulSet is reduced##whenScaled: Retain## @param secondary.persistentVolumeClaimRetentionPolicy.whenDeleted Volume retention behavior that applies when the StatefulSet is deleted##whenDeleted: Retain## @param secondary.extraVolumes Optionally specify extra list of additional volumes to the MySQL secondary pod(s)##extraVolumes: []## @param secondary.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the MySQL secondary container(s)##extraVolumeMounts: []## @param secondary.initContainers Add additional init containers for the MySQL secondary pod(s)##initContainers: []## @param secondary.sidecars Add additional sidecar containers for the MySQL secondary pod(s)##sidecars: []## MySQL Secondary Service parameters##service:## @param secondary.service.type MySQL secondary Kubernetes service type##type: NodePort## @param secondary.service.ports.mysql MySQL secondary Kubernetes service port## @param secondary.service.ports.mysqlx MySQL secondary Kubernetes service port mysqlx##ports:mysql: 3306mysqlx: 33060## @param secondary.service.nodePorts.mysql MySQL secondary Kubernetes service node port## @param secondary.service.nodePorts.mysqlx MySQL secondary Kubernetes service node port mysqlx## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport##nodePorts:mysql: ""mysqlx: ""## @param secondary.service.clusterIP MySQL secondary Kubernetes service clusterIP IP## e.g:## clusterIP: None##clusterIP: ""## @param secondary.service.loadBalancerIP MySQL secondary loadBalancerIP if service type is `LoadBalancer`## Set the LoadBalancer service type to internal only## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer##loadBalancerIP: ""## @param secondary.service.externalTrafficPolicy Enable client source IP preservation## ref https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip##externalTrafficPolicy: Cluster## @param secondary.service.loadBalancerSourceRanges Addresses that are allowed when MySQL secondary service is LoadBalancer## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service## E.g.## loadBalancerSourceRanges:##   - 10.10.10.0/24##loadBalancerSourceRanges: []## @param secondary.service.extraPorts Extra ports to expose (normally used with the `sidecar` value)##extraPorts: []## @param secondary.service.annotations Additional custom annotations for MySQL secondary service##annotations: {}## @param secondary.service.sessionAffinity Session Affinity for Kubernetes service, can be "None" or "ClientIP"## If "ClientIP", consecutive client requests will be directed to the same Pod## ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies##sessionAffinity: None## @param secondary.service.sessionAffinityConfig Additional settings for the sessionAffinity## sessionAffinityConfig:##   clientIP:##     timeoutSeconds: 300##sessionAffinityConfig: {}## Headless service properties##headless:## @param secondary.service.headless.annotations Additional custom annotations for headless MySQL secondary service.##annotations: {}## MySQL secondary Pod Disruption Budget configuration## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/##pdb:## @param secondary.pdb.create Enable/disable a Pod Disruption Budget creation for MySQL secondary pods##create: true## @param secondary.pdb.minAvailable Minimum number/percentage of MySQL secondary pods that should remain scheduled##minAvailable: ""## @param secondary.pdb.maxUnavailable Maximum number/percentage of MySQL secondary pods that may be made unavailable. Defaults to `1` if both `secondary.pdb.minAvailable` and `secondary.pdb.maxUnavailable` are empty.##maxUnavailable: ""## @param secondary.podLabels Additional pod labels for MySQL secondary pods##podLabels: {}
## @section RBAC parameters
#### MySQL pods ServiceAccount
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
##
serviceAccount:## @param serviceAccount.create Enable the creation of a ServiceAccount for MySQL pods##create: true## @param serviceAccount.name Name of the created ServiceAccount## If not set and create is true, a name is generated using the mysql.fullname template##name: ""## @param serviceAccount.annotations Annotations for MySQL Service Account##annotations: {}## @param serviceAccount.automountServiceAccountToken Automount service account token for the server service account##automountServiceAccountToken: false
## Role Based Access
## ref: https://kubernetes.io/docs/admin/authorization/rbac/
##
rbac:## @param rbac.create Whether to create & use RBAC resources or not##create: false## @param rbac.rules Custom RBAC rules to set## e.g:## rules:##   - apiGroups:##       - ""##     resources:##       - pods##     verbs:##       - get##       - list##rules: []
## @section Network Policy
#### Network Policy configuration
## ref: https://kubernetes.io/docs/concepts/services-networking/network-policies/
##
networkPolicy:## @param networkPolicy.enabled Enable creation of NetworkPolicy resources##enabled: true## @param networkPolicy.allowExternal The Policy model to apply## When set to false, only pods with the correct client label will have network access to the ports MySQL is## listening on. When true, MySQL will accept connections from any source (with the correct destination port).##allowExternal: true## @param networkPolicy.allowExternalEgress Allow the pod to access any range of port and all destinations.##allowExternalEgress: true## @param networkPolicy.extraIngress [array] Add extra ingress rules to the NetworkPolicy## e.g:## extraIngress:##   - ports:##       - port: 1234##     from:##       - podSelector:##           - matchLabels:##               - role: frontend##       - podSelector:##           - matchExpressions:##               - key: role##                 operator: In##                 values:##                   - frontend##extraIngress: []## @param networkPolicy.extraEgress [array] Add extra ingress rules to the NetworkPolicy## e.g:## extraEgress:##   - ports:##       - port: 1234##     to:##       - podSelector:##           - matchLabels:##               - role: frontend##       - podSelector:##           - matchExpressions:##               - key: role##                 operator: In##                 values:##                   - frontend##extraEgress: []## @param networkPolicy.ingressNSMatchLabels [object] Labels to match to allow traffic from other namespaces## @param networkPolicy.ingressNSPodMatchLabels [object] Pod labels to match to allow traffic from other namespaces##ingressNSMatchLabels: {}ingressNSPodMatchLabels: {}## @section Password update job
##
passwordUpdateJob:## @param passwordUpdateJob.enabled Enable password update job##enabled: false## @param passwordUpdateJob.backoffLimit set backoff limit of the job##backoffLimit: 10## @param passwordUpdateJob.command Override default container command on mysql Primary container(s) (useful when using custom images)##command: []## @param passwordUpdateJob.args Override default container args on mysql Primary container(s) (useful when using custom images)##args: []## @param passwordUpdateJob.extraCommands Extra commands to pass to the generation job##extraCommands: ""## @param passwordUpdateJob.previousPasswords.rootPassword Previous root password (set if the password secret was already changed)## @param passwordUpdateJob.previousPasswords.password Previous password (set if the password secret was already changed)## @param passwordUpdateJob.previousPasswords.replicationPassword Previous replication password (set if the password secret was already changed)## @param passwordUpdateJob.previousPasswords.existingSecret Name of a secret containing the previous passwords (set if the password secret was already changed)previousPasswords:rootPassword: ""password: ""replicationPassword: ""existingSecret: ""## Configure Container Security Context## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container## @param passwordUpdateJob.containerSecurityContext.enabled Enabled containers' Security Context## @param passwordUpdateJob.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container## @param passwordUpdateJob.containerSecurityContext.runAsUser Set containers' Security Context runAsUser## @param passwordUpdateJob.containerSecurityContext.runAsGroup Set containers' Security Context runAsGroup## @param passwordUpdateJob.containerSecurityContext.runAsNonRoot Set container's Security Context runAsNonRoot## @param passwordUpdateJob.containerSecurityContext.privileged Set container's Security Context privileged## @param passwordUpdateJob.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context readOnlyRootFilesystem## @param passwordUpdateJob.containerSecurityContext.allowPrivilegeEscalation Set container's Security Context allowPrivilegeEscalation## @param passwordUpdateJob.containerSecurityContext.capabilities.drop List of capabilities to be dropped## @param passwordUpdateJob.containerSecurityContext.seccompProfile.type Set container's Security Context seccomp profile##containerSecurityContext:enabled: trueseLinuxOptions: {}runAsUser: 1001runAsGroup: 1001runAsNonRoot: trueprivileged: falsereadOnlyRootFilesystem: trueallowPrivilegeEscalation: falsecapabilities:drop: ["ALL"]seccompProfile:type: "RuntimeDefault"## Configure Pods Security Context## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod## @param passwordUpdateJob.podSecurityContext.enabled Enabled credential init job pods' Security Context## @param passwordUpdateJob.podSecurityContext.fsGroupChangePolicy Set filesystem group change policy## @param passwordUpdateJob.podSecurityContext.sysctls Set kernel settings using the sysctl interface## @param passwordUpdateJob.podSecurityContext.supplementalGroups Set filesystem extra groups## @param passwordUpdateJob.podSecurityContext.fsGroup Set credential init job pod's Security Context fsGroup##podSecurityContext:enabled: truefsGroupChangePolicy: Alwayssysctls: []supplementalGroups: []fsGroup: 1001## @param passwordUpdateJob.extraEnvVars Array containing extra env vars to configure the credential init job## For example:## extraEnvVars:##  - name: GF_DEFAULT_INSTANCE_NAME##    value: my-instance##extraEnvVars: []## @param passwordUpdateJob.extraEnvVarsCM ConfigMap containing extra env vars to configure the credential init job##extraEnvVarsCM: ""## @param passwordUpdateJob.extraEnvVarsSecret Secret containing extra env vars to configure the credential init job (in case of sensitive data)##extraEnvVarsSecret: ""## @param passwordUpdateJob.extraVolumes Optionally specify extra list of additional volumes for the credential init job##extraVolumes: []## @param passwordUpdateJob.extraVolumeMounts Array of extra volume mounts to be added to the jwt Container (evaluated as template). Normally used with `extraVolumes`.##extraVolumeMounts: []## @param passwordUpdateJob.initContainers Add additional init containers for the mysql Primary pod(s)##initContainers: []## Container resource requests and limits## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/## @param passwordUpdateJob.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if passwordUpdateJob.resources is set (passwordUpdateJob.resources is recommended for production).## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15##resourcesPreset: "micro"## @param passwordUpdateJob.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)## Example:## resources:##   requests:##     cpu: 2##     memory: 512Mi##   limits:##     cpu: 3##     memory: 1024Mi##resources: {}## @param passwordUpdateJob.customLivenessProbe Custom livenessProbe that overrides the default one##customLivenessProbe: {}## @param passwordUpdateJob.customReadinessProbe Custom readinessProbe that overrides the default one##customReadinessProbe: {}## @param passwordUpdateJob.customStartupProbe Custom startupProbe that overrides the default one##customStartupProbe: {}## @param passwordUpdateJob.automountServiceAccountToken Mount Service Account token in pod##automountServiceAccountToken: false## @param passwordUpdateJob.hostAliases Add deployment host aliases## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/##hostAliases: []## @param passwordUpdateJob.annotations [object] Add annotations to the job##annotations: {}## @param passwordUpdateJob.podLabels Additional pod labels## Ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/##podLabels: {}## @param passwordUpdateJob.podAnnotations Additional pod annotations## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/##podAnnotations: {}## @section Volume Permissions parameters
#### Init containers parameters:
## volumePermissions: Change the owner and group of the persistent volume mountpoint to runAsUser:fsGroup values from the securityContext section.
##
volumePermissions:## @param volumePermissions.enabled Enable init container that changes the owner and group of the persistent volume(s) mountpoint to `runAsUser:fsGroup`##enabled: false## @param volumePermissions.image.registry [default: REGISTRY_NAME] Init container volume-permissions image registry## @param volumePermissions.image.repository [default: REPOSITORY_NAME/os-shell] Init container volume-permissions image repository## @skip volumePermissions.image.tag Init container volume-permissions image tag (immutable tags are recommended)## @param volumePermissions.image.digest Init container volume-permissions image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag## @param volumePermissions.image.pullPolicy Init container volume-permissions image pull policy## @param volumePermissions.image.pullSecrets Specify docker-registry secret names as an array##image:registry: docker.iorepository: bitnami/os-shelltag: 12-debian-12-r31digest: ""pullPolicy: IfNotPresent## Optionally specify an array of imagePullSecrets.## Secrets must be manually created in the namespace.## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/## e.g:## pullSecrets:##   - myRegistryKeySecretName##pullSecrets: []## @param volumePermissions.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if volumePermissions.resources is set (volumePermissions.resources is recommended for production).## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15##resourcesPreset: "nano"## @param volumePermissions.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)## Example:## resources:##   requests:##     cpu: 2##     memory: 512Mi##   limits:##     cpu: 3##     memory: 1024Mi##resources: {}
## @section Metrics parameters
#### Mysqld Prometheus exporter parameters
##
metrics:## @param metrics.enabled Start a side-car prometheus exporter##enabled: false## @param metrics.image.registry [default: REGISTRY_NAME] Exporter image registry## @param metrics.image.repository [default: REPOSITORY_NAME/mysqld-exporter] Exporter image repository## @skip metrics.image.tag Exporter image tag (immutable tags are recommended)## @param metrics.image.digest Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag## @param metrics.image.pullPolicy Exporter image pull policy## @param metrics.image.pullSecrets Specify docker-registry secret names as an array##image:registry: docker.iorepository: bitnami/mysqld-exportertag: 0.15.1-debian-12-r35digest: ""pullPolicy: IfNotPresent## Optionally specify an array of imagePullSecrets.## Secrets must be manually created in the namespace.## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/## e.g:## pullSecrets:##   - myRegistryKeySecretName##pullSecrets: []## MySQL metrics container security context## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container## @param metrics.containerSecurityContext.enabled MySQL metrics container securityContext## @param metrics.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container## @param metrics.containerSecurityContext.runAsUser User ID for the MySQL metrics container## @param metrics.containerSecurityContext.runAsGroup Group ID for the MySQL metrics container## @param metrics.containerSecurityContext.runAsNonRoot Set MySQL metrics container's Security Context runAsNonRoot## @param metrics.containerSecurityContext.allowPrivilegeEscalation Set container's privilege escalation## @param metrics.containerSecurityContext.capabilities.drop Set container's Security Context runAsNonRoot## @param metrics.containerSecurityContext.seccompProfile.type Set container's Security Context seccomp profile## @param metrics.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem##containerSecurityContext:enabled: trueseLinuxOptions: {}runAsUser: 1001runAsGroup: 1001runAsNonRoot: trueallowPrivilegeEscalation: falsecapabilities:drop: ["ALL"]seccompProfile:type: "RuntimeDefault"readOnlyRootFilesystem: true## @param metrics.containerPorts.http Container port for http##containerPorts:http: 9104## MySQL Prometheus exporter service parameters## Mysqld Prometheus exporter liveness and readiness probes## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes## @param metrics.service.type Kubernetes service type for MySQL Prometheus Exporter## @param metrics.service.clusterIP Kubernetes service clusterIP for MySQL Prometheus Exporter## @param metrics.service.port MySQL Prometheus Exporter service port## @param metrics.service.annotations [object] Prometheus exporter service annotations##service:type: ClusterIPport: 9104clusterIP: ""annotations:prometheus.io/scrape: "true"prometheus.io/port: "{{ .Values.metrics.service.port }}"## @param metrics.extraArgs.primary Extra args to be passed to mysqld_exporter on Primary pods## @param metrics.extraArgs.secondary Extra args to be passed to mysqld_exporter on Secondary pods## ref: https://github.com/prometheus/mysqld_exporter/## E.g.## - --collect.auto_increment.columns## - --collect.binlog_size## - --collect.engine_innodb_status## - --collect.engine_tokudb_status## - --collect.global_status## - --collect.global_variables## - --collect.info_schema.clientstats## - --collect.info_schema.innodb_metrics## - --collect.info_schema.innodb_tablespaces## - --collect.info_schema.innodb_cmp## - --collect.info_schema.innodb_cmpmem## - --collect.info_schema.processlist## - --collect.info_schema.processlist.min_time## - --collect.info_schema.query_response_time## - --collect.info_schema.tables## - --collect.info_schema.tables.databases## - --collect.info_schema.tablestats## - --collect.info_schema.userstats## - --collect.perf_schema.eventsstatements## - --collect.perf_schema.eventsstatements.digest_text_limit## - --collect.perf_schema.eventsstatements.limit## - --collect.perf_schema.eventsstatements.timelimit## - --collect.perf_schema.eventswaits## - --collect.perf_schema.file_events## - --collect.perf_schema.file_instances## - --collect.perf_schema.indexiowaits## - --collect.perf_schema.tableiowaits## - --collect.perf_schema.tablelocks## - --collect.perf_schema.replication_group_member_stats## - --collect.slave_status## - --collect.slave_hosts## - --collect.heartbeat## - --collect.heartbeat.database## - --collect.heartbeat.table##extraArgs:primary: []secondary: []## Mysqld Prometheus exporter resource requests and limits## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/## We usually recommend not to specify default resources and to leave this as a conscious## choice for the user. This also increases chances charts run on environments with little## resources, such as Minikube. If you do want to specify resources, uncomment the following## lines, adjust them as necessary, and remove the curly braces after 'resources:'.## @param metrics.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if metrics.resources is set (metrics.resources is recommended for production).## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15##resourcesPreset: "nano"## @param metrics.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)## Example:## resources:##   requests:##     cpu: 2##     memory: 512Mi##   limits:##     cpu: 3##     memory: 1024Mi##resources: {}## Mysqld Prometheus exporter liveness probe## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes## @param metrics.livenessProbe.enabled Enable livenessProbe## @param metrics.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe## @param metrics.livenessProbe.periodSeconds Period seconds for livenessProbe## @param metrics.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe## @param metrics.livenessProbe.failureThreshold Failure threshold for livenessProbe## @param metrics.livenessProbe.successThreshold Success threshold for livenessProbe##livenessProbe:enabled: trueinitialDelaySeconds: 120periodSeconds: 10timeoutSeconds: 1successThreshold: 1failureThreshold: 3## Mysqld Prometheus exporter readiness probe## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes## @param metrics.readinessProbe.enabled Enable readinessProbe## @param metrics.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe## @param metrics.readinessProbe.periodSeconds Period seconds for readinessProbe## @param metrics.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe## @param metrics.readinessProbe.failureThreshold Failure threshold for readinessProbe## @param metrics.readinessProbe.successThreshold Success threshold for readinessProbe##readinessProbe:enabled: trueinitialDelaySeconds: 30periodSeconds: 10timeoutSeconds: 1successThreshold: 1failureThreshold: 3## Prometheus Service Monitor## ref: https://github.com/coreos/prometheus-operator##serviceMonitor:## @param metrics.serviceMonitor.enabled Create ServiceMonitor Resource for scraping metrics using PrometheusOperator##enabled: false## @param metrics.serviceMonitor.namespace Specify the namespace in which the serviceMonitor resource will be created##namespace: ""## @param metrics.serviceMonitor.jobLabel The name of the label on the target service to use as the job name in prometheus.##jobLabel: ""## @param metrics.serviceMonitor.interval Specify the interval at which metrics should be scraped##interval: 30s## @param metrics.serviceMonitor.scrapeTimeout Specify the timeout after which the scrape is ended## e.g:## scrapeTimeout: 30s##scrapeTimeout: ""## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#relabelconfig##relabelings: []## @param metrics.serviceMonitor.metricRelabelings MetricRelabelConfigs to apply to samples before ingestion## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#relabelconfig##metricRelabelings: []## @param metrics.serviceMonitor.selector ServiceMonitor selector labels## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration#### selector:##   prometheus: my-prometheus##selector: {}## @param metrics.serviceMonitor.honorLabels Specify honorLabels parameter to add the scrape endpoint##honorLabels: false## @param metrics.serviceMonitor.labels Used to pass Labels that are used by the Prometheus installed in your cluster to select Service Monitors to work with## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#prometheusspec##labels: {}## @param metrics.serviceMonitor.annotations ServiceMonitor annotations##annotations: {}## Prometheus Operator prometheusRule configuration##prometheusRule:## @param metrics.prometheusRule.enabled Creates a Prometheus Operator prometheusRule (also requires `metrics.enabled` to be `true` and `metrics.prometheusRule.rules`)##enabled: false   #这里普罗修斯监控,我没开启## @param metrics.prometheusRule.namespace Namespace for the prometheusRule Resource (defaults to the Release Namespace)##namespace: ""## @param metrics.prometheusRule.additionalLabels Additional labels that can be used so prometheusRule will be discovered by Prometheus##additionalLabels: {}## @param metrics.prometheusRule.rules Prometheus Rule definitions##  - alert: Mysql-Down##    expr: absent(up{job="mysql"} == 1)##    for: 5m##    labels:##      severity: warning##      service: mysql##    annotations:##      message: 'mysql instance {{`{{`}} $labels.instance {{`}}`}}  is down'##      summary: mysql instance is down##rules: []

3、创建mysql-secret

apiVersion: v1
kind: Secret
metadata:name: mysql-secretnamespace: mysql8labels:app: mysql
type: Opaque
data:password: MTIzNDU2 # echo -n "123456"mysql-root-password: MTIzNDU2mysql-replication-password: MTIzNDU2

4、安装

#创建ns
kubectl create ns mysql8
#创建secretkubectl create -f mysql-secret.yaml#安装mysql8helm install mysql ./mysql -n mysql8 #查看资源kubectl get all -n mysql8

 

相关文章:

Helm安装Mysql8主从复制集群

目录 一、Helm安装 二、安装mysql 1、拉取镜像 2、修改配置文件 3、创建mysql-secret 4、安装 一、Helm安装 这里不再赘叙&#xff0c;具体安装请参考官网 Helm | 快速入门指南 二、安装mysql 1、拉取镜像 #添加仓库 helm repo add bitnami https://charts.bitnami.c…...

嵌入式基础:Linux C语言:Day7

重点&#xff1a; strlen()函数\strcpy()函数\strcat实现\strcmp()实现 数组的清空&#xff1a;bzero函数、memset函数 一、字符数组 <1> 概念 字符数组本质上就是一个数组&#xff0c;保存一个个字符&#xff0c;也一般用来保存字符串 字符串由多个字符组成的一个字符…...

Tablesaw封装Plot.ly实现数据可视化

上文介绍tablesaw的数据处理功能&#xff0c;本文向你展示其数据可视化功能&#xff0c;并通过几个常用图表示例进行说明。 Plot.ly包装 可视化是数据分析的重要组成部分&#xff0c;无论你只是“查看”新数据集还是验证机器学习算法的结果。Tablesaw是一个开源、高性能的Java…...

RAG与Embedding:现代NLP的核心技术

本篇文章简单梳理我在了解RAG以及Embedding技术时的想法&#xff0c;仅供参考 文章目录 1. 引言背景为什么要关注RAG与Embedding技术 2. 基础概念与原理2.1 什么是RAG (Retrieval-Augmented Generation)定义工作流程优点与适用场景 2.2 什么是Embedding定义作用 3. Embedding在…...

力扣每日一题 - 1812. 判断国际象棋棋盘中一个格子的颜色

题目 还需要你前往力扣官网查看详细的题目要求 地址 1.给你一个坐标 coordinates &#xff0c;它是一个字符串&#xff0c;表示国际象棋棋盘中一个格子的坐标。下图是国际象棋棋盘示意图。2.如果所给格子的颜色是白色&#xff0c;请你返回 true&#xff0c;如果是黑色&#xff…...

Map 那些事儿

1. map 的基本结构 Go 的 map 是一种哈希表&#xff0c;其核心思想是通过哈希函数将键映射到某个位置&#xff08;桶&#xff09;以存储对应的值。它主要包含以下关键部分&#xff1a; •桶&#xff08;bucket&#xff09;&#xff1a;存储键值对的容器&#xff0c;map 中的元…...

GCP Case:MountKirk Games

游戏后端 根据游戏活动动态放大或缩小。 连接到托管的nos0l数据库服务。 运行定制的linux发行版。 游戏分析平台 根据游戏活动来扩大或缩小规模直接处理来自游戏服务器的传入数据。 处理由于移动网络缓慢而迟到的数据。 通过sql查询来访问至少10tb的历史数据 处理由用户…...

[创业之路-187]:《华为战略管理法-DSTE实战体系》-1-从UTStarcom的发展历程,如何辩证的看企业初期发展太顺利中的危机

目录 一、UTStarcom&#xff08;UT斯达康&#xff09;的发展历程 1、创立与初期发展 2、快速成长与上市 3、技术创新与业务拓展 4、战略调整与持续发展 二、从UTStarcom的发展历程&#xff0c;如何辩证的看企业初期发展太顺利中的危机 1、企业初期发展的顺利表现 2、顺…...

高级数据结构-树状数组

介绍 树状数组的推导 两个基础操作 模板-acwing795. 前缀和 #include<bits/stdc.h> using namespace std;const int N 1e610; int c[N]; int lowbit(int x){return x & -x; }int query(int x){int ans 0;for(; x; x - lowbit(x)) ans c[x];return ans; }void add…...

LeetCode279. 完全平方数(2024冬季每日一题 27)

给你一个整数 n &#xff0c;返回 和为 n 的完全平方数的最少数量 。 完全平方数 是一个整数&#xff0c;其值等于另一个整数的平方&#xff1b;换句话说&#xff0c;其值等于一个整数自乘的积。例如&#xff0c;1、4、9 和 16 都是完全平方数&#xff0c;而 3 和 11 不是。 …...

Scala 隐式转换

object test {//复习隐式转换&#xff1a;//隐式转换&#xff1a;编译器 偷偷地&#xff0c;自动地帮我们把一种数据转换为另一种类型//例如&#xff1a;int --> double//它有失败的时候&#xff08;double --> int&#xff09;&#xff0c;有成功的时候//当它转换失败的…...

K8S命令部署后端(流水线全自动化部署)

前言 本文为链接: 云效流水线k8s半自动部署java&#xff08;保姆级&#xff09;的补充,本文起初的目的是为了补充完善k8s流水线的全自动化部署,但是也适用于k8s的一键重启,因为使用k8s的web页面容易出现漏点的情况,因此也可以把代码保存为shell脚本,同样可以实现一键重启。关于…...

Ubuntu中配置交叉编译工具的三条命令的详细研究

关于该把下面的三条交叉编译配置语句加到哪里&#xff0c;详情见 https://blog.csdn.net/wenhao_ir/article/details/144326545 的第2点。 现在试解释下面三条交叉编译配置语句&#xff1a; export ARCHarm export CROSS_COMPILEarm-buildroot-linux-gnueabihf- export PATH$…...

【PyQt5教程 二】Qt Designer 信号与槽的使用方法及PyQt5基本小部件说明

目录 一、信号与槽机制&#xff1a; 二、信号与槽使用方法&#xff1a; &#xff08;1&#xff09;使用Qt Designer 的信号与槽编辑器&#xff1a; &#xff08;2&#xff09;使用固定语法直接建立信号槽连接&#xff1a; 三、PyQt小部件及其触发信号&#xff1a; &#x…...

编程语言中接口(Interface)介绍

编程语言中接口&#xff08;Interface&#xff09;介绍 在编程语言中&#xff0c;“接口”&#xff08;Interface&#xff09;是一种抽象类型&#xff0c;定义了一组方法&#xff08;和属性&#xff09;&#xff0c;但不包含其具体实现。接口通常用于规定类必须实现的行为&…...

算法学习之贪心算法

前言 记录一下&#xff0c;免得又又忘了 贪心算法 在刚接触的时候&#xff0c;我一直觉得贪心和动态规划有相似之处&#xff0c;但做过的题目看&#xff0c;贪心似乎不用迭代...

【jvm】垃圾回收的优点和原理

目录 1. 说明2. 优点3. 原理3.1 发现无用对象3.2 回收无用对象所占用的内存 4. 回收算法4.1 标记-清除算法4.2 复制算法4.3 标记-整理算法4.4 分代收集算法 1. 说明 1.JVM&#xff08;Java虚拟机&#xff09;垃圾回收是Java语言的一大特性&#xff0c;它自动管理内存&#xff…...

YOLO系列发展历程:从YOLOv1到YOLO11,目标检测技术的革新与突破

文章目录 前言一、YOLOv1&#xff1a;单阶段目标检测的开端二、YOLOv2&#xff1a;更精准的实时检测三、YOLOv3&#xff1a;阶梯特征融合四、YOLOv4&#xff1a;性能和速度的新平衡五、YOLOv5&#xff1a;易用性和扩展性的加强六、YOLOv6&#xff1a;工业部署的利器七、YOLOv7&…...

深入浅出:序列化与反序列化的全面解析

文章目录 1. 引言2. 什么是序列化&#xff1f;2.1 为什么需要序列化&#xff1f; 3. 什么是反序列化&#xff1f;3.1 反序列化的重要性 4. 序列化与反序列化的实现4.1 JSON (JavaScript Object Notation)4.2 XML (eXtensible Markup Language)4.3 Protocol Buffers (Protobuf)4…...

word实践:正文/标题/表图等的共用模板样式设置

说在前面 最近使用word新建文件很多&#xff0c;发现要给大毛病&#xff0c;每次新建一个word文件&#xff0c;标题/正文的字体、大小和间距都要重新设置一遍&#xff0c;而且每次设置这些样式都忘记了参数&#xff0c;今天记录一下&#xff0c;以便后续方便查看使用。现在就以…...

Blender中使用BlenderGIS插件快速生成城市建筑模型

导入下载 BlenderGIS 插件 去github上下载其压缩包&#xff0c;地址如下&#xff1a; https://github.com/domlysz/BlenderGIS 在BlenderGIS中导入这个插件压缩包&#xff1a; 点击上方菜单栏的编辑&#xff0c;点击偏好设置 在插件>从磁盘安装中导入刚刚下载的压缩包 可…...

【单元测试】单元测试的重要性

1一些错误的认识 在实际的单元测试过程中总会有一些错误的认识左右着我们&#xff0c;使之成为单元测试最大的障碍&#xff0c;在此将其一一分析如下&#xff1a; 它太浪费时间了&#xff0c;现在要赶进度&#xff0c;时间上根本不允许&#xff0c;或者随便做做应付领导。 …...

Codeforces Round 992 (Div. 2)

这场cf只在b卡了一下&#xff0c;因为b真是犯蠢了&#xff0c;我以为会向下取整&#xff0c;结果是完全就不取整&#xff0c;或者说是向上取整&#xff0c;卡了我半个小时&#xff0c;要不是紧急看了题一下&#xff0c;昨天那场就毁了 话不多说&#xff0c;直接开讲 A. Game …...

el-table一键选择全部行,切换分页后无法勾选

el-table一键全选&#xff0c;分页的完美支持 问题背景尝试解决存在问题问题分析 解决方案改进思路如下具体代码实现如下 问题背景 现在有个需求&#xff0c;一个表格有若干条数据(假设数量大于20&#xff0c;每页10条&#xff0c;保证有2个以上分页即可)。 现在需要在表格上方…...

负载均衡最佳实践及自定义负载均衡器

文章目录 负载均衡最佳实践及自定义负载均衡器一、负载均衡概述二、轮询负载均衡器&#xff08;一&#xff09;理论介绍&#xff08;二&#xff09;Java 实现示例&#xff08;三&#xff09;关键步骤&#xff08;四&#xff09;流程图 三、随机负载均衡器&#xff08;一&#x…...

大模型 LMDeploy 量化部署

1 模型部署 定义&#xff1a; 在软件工程中&#xff0c;部署通常指的是将开发完毕的软件投入使用的过程。在人工智能领域&#xff0c;模型部署是实现深度学习算法落地应用的关键步骤。简单来说&#xff0c;模型部署就是将训练好的深度学习模型在特定环境中运行的过程。 场景…...

算法设计5_分支限界法

分支限界法 分支限界法常以广度优先或以最小耗费(最大效益)优先的方式搜索问题的解空间树&#xff0c;裁剪那些不能得到最优解的子树以提高搜索效率。 步骤&#xff1a; ① 定义解空间(对解编码); ② 确定解空间的树结构&#xff1b; ③ 按BFS等方式搜索&#xff1a; a.每个活…...

2025年人工智能专业可以考哪些证书呢?

人工智能是目前全球热门的专业领域之一&#xff0c;随着人工智能应用范围的不断扩大&#xff0c;越来越多的人开始关注人工智能相关证书的获取。那么&#xff0c;人工智能专业可以考什么证书呢&#xff1f;本文将为大家介绍人工智能相关证书的种类。 人工智能机器视觉应用工程师…...

仿真技术助力高尔夫球打破传统设计局限,实现球杆强大的功能

Altair近日宣布与业内领先的高尔夫装备制造商 Cleveland Golf 开展合作&#xff0c;以设计新款 HiBore XL 球杆。借助 Altair 先进的仿真与设计技术&#xff0c;Cleveland Golf 不断刷新高尔夫装备的行业标准&#xff0c;并在球杆产品设计方面实现突破。 Cleveland Golf 借助 A…...

微前端架构学习笔记

前言 之前遇到过一个需求&#xff0c;有两个项目分别由两个不同的部门负责&#xff0c;不同技术栈&#xff0c;不同代码仓库&#xff1a; A 项目是官网&#xff0c;负责展示产品亮点等信息&#xff0c;有多个入口可以进入 B 项目中的不同页面。B 项目是业务线&#xff0c;负责…...