[JIRA] (JENKINS-52912) Max connections to Kubernetes API fails to validate with "This URL requires POST"

14 views
Skip to first unread message

jenkins-ci@carlossanchez.eu (JIRA)

unread,
Aug 7, 2018, 10:33:01 AM8/7/18
to jenkinsc...@googlegroups.com
Carlos Sanchez updated an issue
 
Jenkins / Bug JENKINS-52912
Max connections to Kubernetes API fails to validate with "This URL requires POST"

The error is displayed in the config page but the changes can be saved anyway

Change By: Carlos Sanchez
Summary: Max connections to Kubernetes API - Kubernetes plugin configuration on jenkins fails to validate with "This URL requires POST"
Issue Type: Task Bug
Priority: Blocker Minor
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

tovidya.s@gmail.com (JIRA)

unread,
Aug 9, 2018, 1:02:02 AM8/9/18
to jenkinsc...@googlegroups.com
Vidya Subramanyam commented on Bug JENKINS-52912
 
Re: Max connections to Kubernetes API fails to validate with "This URL requires POST"

Yes the changes can be saved. But this jenkins is running on a kubernetes cluster and the automatic authentication is failing. I have to do a client configuration on my jenkins system to use any kubectl command. Can you please tell me, what this error means and how to get rid of this??

tovidya.s@gmail.com (JIRA)

unread,
Aug 10, 2018, 1:26:02 AM8/10/18
to jenkinsc...@googlegroups.com

Looks like this is caused by the kubernetes plugin. The version of my kubernetes plugin is 1.12.2. Also downgraded it to 1.10.1 but of no use.

sharkannon@gmail.com (JIRA)

unread,
Aug 15, 2018, 12:29:02 PM8/15/18
to jenkinsc...@googlegroups.com

Seeing this issue as well, 

Jenkins 2.121.2 (LTS)

Kubernetes Plugin: 1.10.1+, 1.12.x (Upgraded and downgraded to no avail)

Kubernetes: 1.10.5 (on GKE)

NGINX: 1.15.2 (SSL Proxy in front of Jenkins

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:43:27 PM7/16/19
to jenkinsc...@googlegroups.com
Jesse Glick assigned an issue to Unassigned
 
Change By: Jesse Glick
Assignee: Carlos Sanchez
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages