Skip to content
This repository has been archived by the owner on Aug 28, 2021. It is now read-only.

Check doesn't work with TLS and token_path #107

Open
xdom opened this issue Mar 13, 2019 · 3 comments
Open

Check doesn't work with TLS and token_path #107

xdom opened this issue Mar 13, 2019 · 3 comments
Labels

Comments

@xdom
Copy link

xdom commented Mar 13, 2019

Hi,
we have the resource configured with cluster_url, cluster_ca and namespace resource parameters. Then we only use put with token_path (and other params related to deployment).
However, check is scheduled even if no get is set up but it cannot authenticate against Kubernetes, obviously:

resource script '/opt/resource/check []' failed: exit status 1

stderr:
Initializing kubectl...
Cluster "default" set.
User "admin" set.
Context "default" modified.
Switched to context "default".
error: tls: failed to find any PEM data in certificate input

Although this doesn't cause any problems with put, it makes resource square orange (failing). This is not documented. Could you suggest anything to deal with this?

@lainthelame
Copy link

Having the same issue.

@ghost
Copy link

ghost commented Apr 18, 2019

We're having the same issue with PUT

@msiegenthaler
Copy link
Member

We fixed some stuff around check with dynamic resource configs in 2.14.0-1, is your check still yellow?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants