GKE deployment from Jenkins Issues - jenkins

While deploying the GKE from Jenkins we are getting below error in jenkins console.
Failed to verify apps/v1/Deployment: app-test
java.io.IOException: Failed to launch command args: [kubectl, --kubeconfig, /var/lib/jenkins/workspace/sample_dev_gke_deploy#tmp/.kube14897892684774139622config, get, deployment, app-test, -o, json], status: 1. Logs: Error from server (NotFound): deployments.apps "app-test" not found
This seems to be an issue as discussed in Similar issue any idea if this issue is resolved. Please let us know if any further details required ?
Thanks in advance
GKE deployment from Jenkins. Manual GKE deployment works fine.

Related

Error on etcd health check while setting up RKE cluster

i'm trying to set up a rke cluster, the connection to the nodes goes well but when it starts to check etcd health returns:
failed to check etcd health: failed to get /health for host [xx.xxx.x.xxx]: Get "https://xx.xxx.x.xxx:2379/health": remote error: tls: bad certificate
If you are trying to upgrade the RKE and facing this issue then it could be due to the missing of kube_config_<file>.yml file from the local directory when you perform rke up.
This similar kind of issue was reported and reproduced in this git link . Can you refer to the work around and reproduce it by using the steps provided in the link and let me know if this works.
Refer to this latest SO and doc for more information.

How to connect local kubernetes with local jenkins

My kubernetes environment is running on kind while my jenkins environment is running as a docker instance. I tried watching all of the youtube tutorial regarding this and have followed all of the steps carefully but still, I can't seem to get past this very specific error. This error doesn't appear to any of the youtube tutorial I watched and it's very frustrating.
Error testing connection https://127.0.0.1:53883: java.net.ConnectException: Failed to connect to /127.0.0.1:53883
The URL is from running the command: kubectl cluster-info

Error from server (NotFound): deployments.apps

I am trying to do blue green deployments for AKS using Jenkins. I am currently following this document
https://learn.microsoft.com/en-us/azure/developer/jenkins/deploy-to-aks-using-blue-green-deployment-pattern
When I run the pipeline I am getting the following error:
kubectl --kubeconfig=kubeconfig delete deployment todoapp-deployment-blue
Error from server (NotFound): deployments.apps "todoapp-deployment-blue" not found
What exactly does this error mean and how do I resolve it.
This error means that there is no deployment called todoapp-deployment-blue in your kubernetes namespace and you need to create it first (to delete it, lol).

Jenkins and IBM Udeploy connection issue 503 error

Hi iam trying to integrate jenkins with Udeploy server.
When i test the connection using IBM UrbanCode Deploy Pipeline Plugin Configuration and the test connection option iam getting the below error
Error connecting to IBM UrbanCode Deploy: 503using URI: https://udeploy.oe.company/rest/state
I could confirm there is no issue with firewall. i am able to do a curl successfully to the url.
Iam not able to see anything in jenkins logs.
https://jenkinsurl.org/log/all
is there anyway i could check the logs of the plugin to see what is happening during connection?
Any help appreciated.
You might have an SSL issue. If using self-signed certs, try swapping the self signed certs. Note that Urbancode might be using the IBM JDK which has its own truststore, and you'll need to store the Jenkins certs there.

Jenkins issue with marathon deployment plugin

I've followed the https://docs.mesosphere.com/1.8/usage/tutorials/deploy-on-marathon/ guide for deploying an app from jenkins to marathon on dcos. I'm using a private registry hosted inside the dcos, and jenkins as well.
I'm getting the following output from jenkins console output,
[Marathon] Failed to update Marathon application:
[Marathon] Unauthorized (http status: 401)
any idea whats wrong?
I tried to create the app manually via marathon ui and it works fine.
Just got the url all wrong, it should be http://leader.mesos:8080/

Resources