Dusty Mabe
Dusty Mabe
I can confirm that the workaround in https://github.com/digitalocean/csi-digitalocean/issues/328#issuecomment-666513011 still works for me today.
@rtnpro ^^ do you mind taking a look at this?
looks like the "detection" that atomicapp is running on openshift and the special behavior that results was affected by 1a37ab8 after that commt the `self.access_token = os.environ['TOKEN_ENV_VAR']` is no longer...
link to the commit that fixed this in kubeshift?
also would be good to post a link to the error you see. with `0.6.3` and `insecure-skip-tls-verify: true` and you see: ``` [vagrant@rhel-cdk try]$ sudo atomic run padapp ./ docker...
workaround for now is to add `insecure-skip-tls-verify: true` to your ~/.kube/config file.
Is the problem slurped console logs or is it the process running `journalctl`. If it's the latter then `SYSTEMD_LOG_COLOR` could be used by the aggregator instead? I'd prefer not to...
> SYSTEMD_LOG_COLOR which I guess is different from `SYSTEMD_COLORS` and only applies to console logs?
> > I'd prefer not to differ from Fedora here if we don't really need to. > > This is a good point. But note: I think this is a...
I'm still kind of torn on this. As a human who often (almost every weekday of my life) looks at serial console and VGA console (not just the logs but...