Environment variable MYSQL_HISTFILE is added to mariadb container
to disable storing client mysql history to ~/.mysql_history file.
Change-Id: Ie95bc1f830fbf34d30c73de07513299115d8e8c5
When autoscaling is disabled after pools are created, there is an
opportunity for some autoscaling to take place before autoscaling
is disabled. This change checks to see if autoscaling needs to be
disabled before creating pools, then checks to see if it needs to
be enabled after creating pools. This ensures that autoscaling
won't happen when autoscaler is disabled and autoscaling won't
start prematurely as pools are being created when it is enabled.
Change-Id: I8803b799b51735ecd3a4878d62be45ec50bbbe19
fsGroup is not supported inside the container securityContext,
only inside the pod. This drops a configuration that is not
valid and makes things deployable.
Change-Id: I956a1de107768c3fadc704722db83eb661cd25d2
The autoscaler was introduced in the Nautilus release. This
change only sets the pg_num value for a pool if the autoscaler
is disabled or the Ceph release is earlier than Nautilus.
When pools are created with the autoscaler enabled, a pg_num_min
value specifies the minimum value of pg_num that the autoscaler
will target. That default was recently changed from 8 to 32
which severely limits the number of pools in a small cluster per
https://github.com/rook/rook/issues/5091. This change overrides
the default pg_num_min value of 32 with a value of 8 (matching
the default pg_num value of 8) using the optional --pg-num-min
<value> argument at pool creation and pg_num_min value for
existing pools.
Change-Id: Ie08fb367ec8b1803fcc6e8cd22dc8da43c90e5c4
Challenge:
Now remote_ks_admin and remote_rgw_user are using for user labels
of backup target openstack cloud.
When the backup user doesn't exist and we can enable job_ks_user
manifest.
But job_ks_user uses .Vaules.secrets.identity.admin and mariadb,
while secret-rgw and cron-job-backup-mariadb use .Values.secrets.
identity.remote_ks_admin and remote_rgw_user.
It requires to use same values for admin and remote_ks_admin,
and for mariadb and remote_rgw_user.
Seems it isbreaking values consistency.
Suggestion:
Now providing 2 kinds of backup - pvc and swift.
"remote_" means the swift backup.
In fact, mariadb chart has no case to access to keystone except
swift backup. So we can remove remote_xx_* prefix and there is
no confusion.
Change-Id: Ib82120611659bd36bae35f2e90054642fb8ee31f
- Uplifts the image to nginx 0.42.0 to address CVEs
- Updates nginx.tmpl accordingly for nginx 0.42.0
- Adds CLusterRole and labels needed for nginx 0.42.0
- Updates release notes for mariadb
Change-Id: Ie4e2a66873bc130c547ff8f30d8e1b2ee9a62186
This change removes the ignore-errors parameter for the
linter in order to enforce release note updates per chart
change.
Change-Id: I15f538be3c4ad253d5c4f64c21c0b1df10e7e5d2
This patchset updates grafana chart manifests to enable TLS with
osh-infra mariadb. TLS for osh-infra mariadb is completed as part
of TLS phase 1, no additional mariadb chart work is required to
work with this patch.
Change-Id: Ic01e7c012ab2167d59b2117eb985386666f2bb2a
- Add application label using service name
- Add before-hook-creation delete policy as a default
(It is a default one in helmv3)
- Add custom metadata by passing params
Change-Id: Ie09f8491800031b9ff051a63feb3e018cb283342
About zookeeper chart,It's been removed,But there are still some related scripts that have not been completely deleted,we should remove them.
Change-Id: Iae20717482ad6c7a40f54174eef120d094abbd59
This change updates the releasenotes for the ldap chart to the
latest version of the chart as of this patchset.
Change-Id: I8c22fb3a7b0c6235e7179d96e32c1f160bf08ed2
Currently pool quotas and pg_num calculations are both based on
percent_total_data values. This can be problematic when the amount
of data allowed in a pool doesn't necessarily match the percentage
of the cluster's data expected to be stored in the pool. It is
also more intuitive to define absolute quotas for pools.
This change adds an optional pool_quota value that defines an
explicit value in bytes to be used as a pool quota. If pool_quota
is omitted for a given pool, that pool's quota is set to 0 (no
quota).
A check_pool_quota_target() Helm test has also been added to
verify that the sum of all pool quotas does not exceed the target
quota defined for the cluster if present.
Change-Id: I959fb9e95d8f1e03c36e44aba57c552a315867d0
This change updates the releasenotes for the elasticsearch chart to the latest version of the chart as of this patchset.
Change-Id: Idd4180993775807ebcef3e7879afb2f8ab42148c
When using helm3 to deploy, it fails as helm 3
no longer supports rbac.authorization.k8s.io/v1beta1,
but v1 can support helm2 and helm3 (liujinyuan@inspur.com).
Change-Id: I8e0ceb0c0991fd48b5b6a1b688a5c1b91f58c02e
This reverts commit 910ed906d0df247f826ad527211bc86382e16eaa.
Reason for revert: May be causing upstream multinode gates to fail.
Change-Id: I1ea7349f5821b549d7c9ea88ef0089821eff3ddf
When using a helm3 to deploy , it fails. Helm3 no more support rbac.authorization.k8s.io/v1beta1 , but v1 can support helm2 and helm3.
Change-Id: I2760befdc20e73989bce5cc581d086de57f91383
When using a helm3 to deploy , it fail! Helm3 no more support rbac.authorization.k8s.io/v1beta1 , but v1 can support helm2 and helm3.This change optimized deployment.
Change-Id: I41ca3ee2490eadce8d043cf6a757bf8569f31931
This change updates the releasenotes for the libvirt chart to the latest version of the chart as of this patchset.
Change-Id: I055c69b4c5a266641b4684a94a46675475f27409
Grafana v7.3 has ability to add the customized dashboard as homepage.
This removes the necessity to have explicit job to add a homepage.
Clean up the explicit add_home-dashboard job.
Change-Id: I68baa7693f545e2d91dba01ae61b4bdae8a26bee
Update the elasticsearch-master statefulset to use the correct
helm-toolkit snippet for the update strategy.
Change-Id: Ifd07a13cc63f1ba610a3f70052ec64be9db3b09c
