-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Hi @ryandawsonuk, However what is needed when using KIND is to install Rancher Local Path Provisioner as mentionned here. Did you installed it? |
Yeah I'm running the local path provisioner. Am wondering if it might be something to do with the new KIND. I found that the old removed initContainer actually doesn't work either - it has to set runAsUser too. I'm using KIND 0.7.0 to create a 1.15 cluster. Or could be related to something else in my KIND config. |
Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. To track this PR (even if closed), please open a corresponding issue if one does not already exist. |
This PR has been automatically closed because it has not had recent activity since being marked as stale. Please reopen when work resumes. |
Hi @ryandawsonuk, As I didn't have time to answer you before I was able to take some time today to try to reproduce with a new Kind version (v0.8.1) and default Kind config. I couldn't reproduce your
At first sight your config look fine but I'm not an KIND expert. In addition, it seems that Kind >= 0.7.0 don't need anymore I'll create a PR to update |
Cool, thanks for following this up |
Otherwise get AccessDeniedException when running on KIND 0.7.0. See #363