io.fabric8.kubernetes.client.KubernetesClientException

An error has occurred.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web86

  • An error has occurred.
  • An error has occurred.
  • via GitHub by ntrvic
    , 11 months ago
    An error has occurred.
  • Stack trace

    • io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred. at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:57) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.create(BaseOperation.java:234) at com.aruba.test.test_app.main(test_app.java:117) Caused by: javax.net.ssl.SSLPeerUnverifiedException: Hostname kubernetes.default.svc not verified: certificate: sha1/pn3xC0EodJTjGo5zetEr8QSgnyo= DN: CN=kube-apiserver I have 1 sentinel node (unbuntu vm) + 3 nodes (coreos). I have another Ubuntu in which I ran ansible script where sentinel and nodes IP addresses are configure. suggestions please. On Sat, May 14, 2016 at 2:29 PM, Pradeep Ganachari < ganachar...@gmail.com> wrote: Thanks for your inputs. Need your help with recreation of api server certificate . Kubernetes has been deployed as below. As I am new to this, kindly excuse if any wrong in explanation. :) 3 nodes (core os) + 1 sentinel (ubuntu vm.) kubectl, kubelet, kube-apiserver are in sentinel. application(replicationcontroller) which creates kube job is created using ./kubectl in sentinel. On Sat, May 14, 2016 at 1:55 PM, Jimmi Dyson <jimmi...@gmail.com> wrote: The error indicates that the certificate isn't valid for kubernetes.default.svc. We've been recommended by kubernetes maintainers that this is the canonical address for pods contacting the api server from inside a cluster. There are a few ways to fix/workaround this. First option (best option) is to recreate your api server certificate with the addition of kubernetes.default.svc as a valid hostname. How you do that depends on how you've deployed kubernetes. If you need help with that, let us know how you deployed it & we can try to help with that if we've seen it before. Second option, which I would only use for development environments personally, is to disable certificate validation. Note that this opens you up for man in the middle attacks so be careful where you use it (& don't use it if at all possible!). To disable certificate validation, set the environment variable KUBERNETES_TRUST_CERTIFICATES to true in the pod/shell you're running your app. On 09:04, Sat, 14 May 2016 Pradeep Ganachari, < ganachar...@gmail.com> wrote: I have resolved the above issue. there was some problem with my build.sbt it seems. now I am getting below exception. FAILED: io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred. io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred. ... 3 more Caused by: javax.net.ssl.SSLPeerUnverifiedException: Hostname kubernetes.default.svc not verified:* * certificate: sha1/pn3xC0EodJTjGo5zetEr8QSgnyo=* *DN: CN=kube-apiserver* subjectAltNames: [10.3.0.1, 10.22.42.243, kubernetes, kubernetes.default] could you please help me out to resolve this? On Fri, May 13, 2016 at 8:56 PM, James Strachan < james.s...@gmail.com> wrote: On 12 May 2016 at 11:14, Pradeep Ganachari <ganachar...@gmail.com > wrote: Hello, I am trying to create Kubernetes Job using following code. *client.extensions().jobs().inNamespace("aa-system").create(job);* with all necessary data filled in job. Getting following exception. FAILED: *java.lang.IllegalStateException: No adapter available for type:class io.fabric8.kubernetes.client.ExtensionsAPIGroupClient* java.lang.IllegalStateException: No adapter available for type:class io.fabric8.kubernetes.client.ExtensionsAPIGroupClient at io.fabric8.kubernetes.client.BaseClient.adapt(BaseClient.java:135) at io.fabric8.kubernetes.client.DefaultKubernetesClient.extensions(DefaultKubernetesClient.java:214)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.