8c614d4ffd
Manually set Namespace for Sonobuoy's config.json. Sonobuoy's bug forcing heptio-sonobuoy namespace [1] usage only does not impact this Helm chart because the config.json is directly controlled by the `values.yaml` and not Sonobuoy's CLI. Now multiple instances of this chart may exist at once by specifying unique namespaces at helm install time. Modify Sonobuoy test script to install two instances of Sonobuoy Helm chart. Also install readonly serviceaccount to verify it will work with more than one instance simultaneously. [1] https://github.com/heptio/sonobuoy/issues/420 Change-Id: I6d4ecfb812a4312af13abf1e265de495e27967f9 |
||
---|---|---|
.. | ||
010-setup-client.sh | ||
020-deploy-mariadb.sh | ||
030-deploy-rabbitmq.sh | ||
040-deploy-memcached.sh | ||
050-deploy-keystone.sh | ||
060-deploy-ranger.sh | ||
070-deploy-ranger-agent.sh | ||
080-deploy-ceph.sh | ||
085-ceph-ns-activate.sh | ||
090-deploy-shaker.sh | ||
090-radosgw-openstack.sh | ||
100-ingress.sh | ||
sonobuoy.sh | ||
wait-for-pods.sh |