Commit Graph

6 Commits (0622f0482b04a9ea0a2efe45bbadea7951f845e7)

Author SHA1 Message Date
Arvind Iyengar 75481c6cec
Use rancher/shell 2021-06-28 16:57:30 -07:00
Arvind Iyengar a93a040b70
Manual changes to Monitoring for rebase 2021-06-22 10:30:48 -07:00
Arvind Iyengar 3202417f2d
Add dummy openAPIV3Schema to initContainer and log patch 2021-06-16 18:13:27 -07:00
Arvind Iyengar 02ff0c9df8
Move establishing CRD logic to a helper template 2021-06-01 13:58:40 -07:00
Arvind Iyengar 5f3bbe4a36
Mimic Helm CRD install process by introducing wait
As part of the Helm CRD installation process shown [here](43853ea772/pkg/action/install.go (L160-L162)), charts that both attempt to install CRDs and then install resources (e.g. `len(totalItems) > 0`) invalidate the cache and attempt to get the CRDs again to `Give time for the CRD to be recognized.` before continuing the Helm installation.

Because Monitoring V2 currently does not observe this invalidation and wait, flakey race conditions documented in issues like https://github.com/rancher/rancher/issues/32025 and https://github.com/rancher/rancher/issues/29171 can be caused. This commit introduces that invalidation process.
2021-06-01 12:42:26 -07:00
Arvind Iyengar 551327b14e
Checkout current packages from dev-v2.5-source
```bash
git fetch upstream
git checkout upstream/dev-v2.5-source -- packages; git reset HEAD; git checkout -- packages/README.md
```
2021-05-17 15:30:27 -07:00