You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2021. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
Hi,
we have the resource configured with
cluster_url
,cluster_ca
andnamespace
resource parameters. Then we only useput
withtoken_path
(and other params related to deployment).However,
check
is scheduled even if noget
is set up but it cannot authenticate against Kubernetes, obviously: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?The text was updated successfully, but these errors were encountered: