Kimmo Lehto
Kimmo Lehto
Any idea why the validation fails on drone? Works fine on my vagrant. ``` 3645 | [1459-do-master-0] [ERROR] + kubectl get -n kube-system serviceaccount/pharos-admin 3646 | [1459-do-master-0] [ERROR] Unable to...
How about `-a`/`--all`? I think classico had that.
With ` Dry::Validation.Form` the unknown keys disappear from `input` before validation It's quite simple to check for unknown top level keys with: ```ruby unless (yaml.keys.map(&:to_sym) - schema_class.rules.keys).empty? signal_usage_error .. end...
 Doesn't bite when e2e is stuck outside of pharos..
Without something like this, some commands may hang forever. For example, I've had this for an hour now: ``` [host-00] Waiting for etcd to respond ... ```
Can confirm that modifying the lines referenced above to skip ruby extension directories does fix the problem.
@iamsimakov No, one compiled from master.
This, I think, is work-aroundable by using the `-d` parameter to set the temporary path during builds. (You don't have to rebuild rubyc) Maybe if you set it to `/root`...
Yes, but it's still better than /tmp until an option like that is available. You could build inside a chroot jail or a docker container without root.
Both errors tell the same thing, SSL verification failed. Mortar doesn't use `kubectl`. The error message could be more concise or descriptive though.