Job wait cluster was failing due to the field immutability which was
resulting in the manual delete of the job for every helm upgrade to be
successful. Reason being job being upgraded before the other manifest
that are required been updated. It can be avoided by using helm-hook
post-install and post-upgrade which will force the job manifest to be
applied only after all other manifest are applied. Hook annotation is
provided "5" so that the if other jobs are annotated, exporter job will
be last to created in case hooks are added to the other jobs in chart.
Also helm3_hook value is used for condition.
Change-Id: Ib83f1d4bef6300c2b76aa54f08927b74346184c7
exporter-jpb-create-user was failing due to the field immutability
which was resulting in the manual delete of the job for every helm
upgrade to be successful. Reason being job being upgraded before the
other manifest that are required been updated. It can be avoided by
using helm-hook post-install and post-upgrade which will force the
job manifest to be applied only after all other manifest are applied.
Hook annotation is provided "5" so that the if other jobs are annotated,
exporter job will be last to created.
helm3_hook value is used for the condition which will enable the disable
of the hook.
Change-Id: I2039abb5bad07a19fd09fc5e245485c3c772beca
This change configures Ceph daemon pods so that
/var/lib/ceph/crash maps to a hostPath location that persists
when the pod restarts. This will allow for post-mortem examination
of crash dumps to attempt to understand why daemons have crashed.
Change-Id: I53277848f79a405b0809e0e3f19d90bbb80f3df8
This patch removes the dependency on cfssl to generate certificates and
removes unused constructs in the script.
Change-Id: Ia933420157f456bf99a6ec5416e6dbb63bfa5258
Signed-off-by: Tin Lam <t@lam.wtf>
The broker attribute should use a comma separated list with the port
definition included
Example: kafka1:9092,kafka2:9092,kafka:9092
The kafka client will connect to the first available host this
will provide resiliency if a host is not available
Change-Id: I5f82e96f2aa274379b6d808291d4b5109709bf72
Some minor improvements are made in this patchset:
1) Move osd_disk_prechecks to the very beginning to make sure the
required variables are set before running the bulk of the script.
2) Specify variables in a more consistent manner for readability.
3) Remove variables from CLI commands that are not used/set.
Change-Id: I6167b277e111ed59ccf4415e7f7d178fe4338cbd
A deployment that specifies a placement target with "delete: true"
should delete that placement target if it exists. For a clean
deployment the expectation is that the placement target should be
created and immediately deleted; however, the check for existence
happens before its creation and the delete doesn't execute as a
result. This change adds a recheck for existence immediately after
creation to remedy that.
Change-Id: I26f7fa79c5c851070e94af758d0a0438aa7efa52
This test (create and remove test index) already validates that elasticsearch is working correctly. Removed additional check for repo verification for external service like S3 as this seems out of scope since this can be configured differently and causes test to fail.
Change-Id: Ic9328b204c82bdf0e328370d7060a265210c9e8a
The current implementation of the Ceph CSI provisioner is tied too
closely with the older Ceph RBD provisioner, which doesn't let the
deployer deploy Ceph CSI provisioner without the old RBD provisioner.
This patchset will decouple them such that they can be deployed
independently from one another.
A few other changes are needed as well:
1) The deployment/gate scripts are updated so that the old RBD and
CSI RBD provisioners are separately enabled/disabled as needed.
The original RBD provisioner is now deprecated.
2) Ceph-mon chart is updated because it had some RBD storageclass
data in values.yaml that is not needed for ceph-mon deployment.
3) Fixed a couple of bugs in job-cephfs-client-key.yaml where RBD
parameters were being used instead of cephfs parameters.
Change-Id: Icb5f78dcefa51990baf1b6d92411eb641c2ea9e2
- Uplifts the image to nginx 0.42.0 to address CVEs
- Adds labels needed for nginx 0.42.0
- Updates release notes for ingress
Change-Id: I133d6d30d4a68628ee516f5896780cc8096ffd1f
This will ease mirroring capabilities for the docker official images.
Signed-off-by: Thiago Brito <thiago.brito@windriver.com>
Change-Id: I0f9177b0b83e4fad599ae0c3f3820202bf1d450d
1) Removed some remaining unsupported ceph-disk related code.
2) Refactored the code that determines when a disk should be
zapped. Now there will be only one place where disk_zap is
called.
3) Refactored the code that determines when LVM prepare should
be called.
4) Improved the logging within the OSD init files
Change-Id: I194c82985f1f71b30d172f9e41438fa814500601
A new "delete" value has been added to the ceph-rgw placement
target spec to allow existing placement targets to be deleted in a
brownfield deployment. For deployments where a deleted placement
target does not exist, the placement target will be created and
deleted in a single step.
Change-Id: I34e6d97543b63848b267332556b62d50d1865f49
Two new values, "delete" and "delete_all_pool_data," have been
added to the Ceph pool spec to allow existing pools to be deleted
in a brownfield deployment. For deployments where a pool does not
exist, either for greenfield or because it has been deleted
previously, the pool will be created and then deleted in a single
step.
Change-Id: Ic22acf02ae2e02e03b834e187d8a6a1fa58249e7
This ps change the key name for the blackbox exporter so that
it is consistent with the naming convention of other prometheus
exporters.
Co-authored-by: Chi Lo <cl566n@att.com>
Change-Id: Ia190aa6730fab99d7fb14c53b538c72a1bc698ce
This ps updates the version to 7.4.5
The css element in GUI has changed in the new Grafana version , so updated
the selenium script to find the right element.
Change-Id: I972fddf73719fb5bef821679a5ab07491edf55ff
This patch set fixes a wrong source reference in Charts.yaml
in the k8s-keystone-webhook chart.
Change-Id: I51b3b0bec6641a92ccc1b9002d8daef128963c8c
Signed-off-by: Tin <tin@irrational.io>
Remove the TLS_OPTION env from helm-toolkit s3-bucket job. There
can be different option for tls connection, depending on whether
the rgw server is local or remote. This change allows the
create-s3-bucket script to customize its connection argument
which can be pulled from values.yaml.
Change-Id: I2a34c1698e02cd71905bc6ef66f4aefcd5e25e44
