Lab 5.1. Configuring TLS Access
Hello,
in the step 8 of this lab, I created a json file to create a new pod and in the step 9 I used this file curlpod.json to build an XPOST API call to the host using the following command:
[email protected]: ̃$ curl --cert ./client.pem --key ./client-key.pem --cacert ./ca.pem \https://k8scp:6443/api/v1/namespaces/default/pods -XPOST -H'Content-Type: application/json'[email protected]
Attached my CLI : i receive an error 415...I don't understand the reason beause the json file format shall be supported
thx
Alberto.
Comments
-
Hello,
First off if you type a command on a single line you do not need to include the backslashes. That character has special meaning to the shell and could be causing some of your issues. Second make sure you have proper spaces in your command line, it's difficult to tell from the picture, so they could be fine. The third thing I would check is the syntax of the curlpod.json file. Are you using the file from the tarball, or did you type it by hand? If by hand use diff to compare against the tarball and see if there are any differences.
Regards,
0 -
Thanks Serewicz, I solved this issue...but I have another in Exercise 6.1: RESTful API Access:
When I try to see if I can get basic API information from my cluster, using curl command
"[email protected]:~$ curl https://master:6443/apis --header "Authorization: Bearer $token" -k ",
I receive the protocol error:"curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)"
Any idea of error cause?
thanks again,
Alberto.0 -
Hi @albtau81,
Are you able to confirm that the exported token has a value after step 4?
Regards,
-Chris0 -
Hi @chrispokorni,
yes after step 4, I verified the presence of the token in the variable with the echo command.
It seems something related to the protocol used when there is an header in the request..Thanks for help!
0 -
Hello,
Are you running the curl command from a mac? There is a known curl bug I have encountered that only seems to affect mac users.
If not using a mac, are there any errors or indications in the log of the kube-apiserver?
Regards,
0 -
hello,
I am running the command using windows.
Attached snaphots of directory where I am looking for logs and the log file.
Hope it is helpful...
Regards0 -
Hi @albtau81,
curl
may be run using the control-plane node's hostname, its private/internal IP address, and thek8scp
alias. Any success when swapping them?Also, a solution on GitHub for
HTTP/2 stream
errors suggests to add the--http1.1
flag to thecurl
command. Can you try this as well?Regards,
-Chris0 -
Hi @chrispokorni ,
using the command : [email protected]:~$ curl https://k8scp:6443/api/v1 --header "Authorization: Bearer $token" --http1.1 -k,
I receive the 403 error:
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "forbidden: User \"system:anonymous\" cannot get path \"/api/v1\"",
"reason": "Forbidden",
"details": {},
"code": 403There isn' t any success even if I swap control-plane node's hostname (master), its InternalIP ( 10.2.0.4 ), and the k8scp alias.
Regards,
A.0 -
Hi @albtau81,
This error indicates that the token did not include the expected identifying string. This is often caused by the caret "^" sign being mishandled by the terminal. I would recommend typing in the caret "^" manually, especially if copy/pasting the entire command from the PDF lab guide.
Regards,
-Chris2
Categories
- 8.8K All Categories
- 13 LFX Mentorship
- 66 LFX Mentorship: Linux Kernel
- 356 Linux Foundation Boot Camps
- 226 Cloud Engineer Boot Camp
- 69 Advanced Cloud Engineer Boot Camp
- 23 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 727 Training Courses
- 14 LFC110 Class Forum
- 16 LFD102 Class Forum
- 96 LFD103 Class Forum
- 2 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 14 LFD254 Class Forum
- 420 LFD259 Class Forum
- 78 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 15 LFS200 Class Forum
- 683 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 23 LFS241 Class Forum
- 26 LFS242 Class Forum
- 18 LFS243 Class Forum
- 4 LFS244 Class Forum
- 7 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 104 LFS253 Class Forum
- 753 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 48 LFS260 Class Forum
- 75 LFS261 Class Forum
- 6 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 8 LFS268 Class Forum
- 4 LFS269 Class Forum
- 173 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 184 LFW211 Class Forum
- 100 LFW212 Class Forum
- 875 Hardware
- 204 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 716 Linux Distributions
- 78 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 125 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 344 Ubuntu
- 445 Linux System Administration
- 33 Cloud Computing
- 63 Command Line/Scripting
- Github systems admin projects
- 88 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 742 Programming and Development
- 237 Kernel Development
- 471 Software Development
- 898 Software
- 244 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 313 Installation
- 19 All In Program
- 19 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)