Lab10.1 - Error creating ingress rule: "pathType must be specified"
Hi there,
I am working through the LFS258 course and have properly gone through all the labs in sequence successfully up to Lab10.1 so far.
Now, in that Lab exercise, the step 9 (Ingest the ingress rule) fails:
[email protected]:~$ kubectl create -f ingress.rule.yaml error: error validating "ingress.rule.yaml": error validating data: [ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "serviceName" in io.k8s.api.networking.v1.IngressBackend, ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "servicePort" in io.k8s.api.networking.v1.IngressBackend]; if you choose to ignore these errors, turn validation off with --validate=false
When I add the mentioned --validate=false Flag, there is another error:
[email protected]:~$ kubectl create -f ingress.rule.yaml --validate=false The Ingress "ingress-test" is invalid: spec.rules[0].http.paths[0].pathType: Required value: pathType must be specified
I am running on Kubernetes 1.19.6 ... got anything deprecated here?
Thanks for help ..
Comments
-
Hi @wodecker,
There may be several aspects to cause these errors.
The course is asking for Kubernetes v1.19.0 - to keep it aligned with the CKA certification exam environment, and it has not been tested against v1.19.6.
The easiest method to fix your first error and move forward would be to update the
apiVersion
in theingress.rule.yaml
file withapiVersion: networking.k8s.io/v1beta1
, as it is presented in the YAML code on Step 8 of the lab manual. Upgrading theIngress
resource from beta (v1beta1
) to stable (v1
) requires some of the YAML fields to be re-formatted according to the latest documentation, but this method has not been tested and validated against the exercise.For the second error, inspect carefully the YAML code in Step 15, where each
path: /
is followed bypathType: ImplementationSpecific
line. Adding thepathType
should eliminate this error.Between Kubernetes v1.19 and 1.20 the
Ingress
object matured from beta to stable, it introduced changes in the YAML formatting, resulting in inconsistent behaviors betweenIngress
object deployments. This type of behavior is often encountered as objects mature between Kubernetes releases.Regards,
-Chris0 -
Hi @chrispokorni ,
thanks for the quick response. Indeed I discovered that the pathType parameter has been added to the yaml in step 15, but unfortunately it was not yet there in step 8, so I didn't get aware of this on first try ..
But also with that parameter added, there was still an error:
[email protected]:~$ kubectl create -f ingress.rule.yaml --validate=false The Ingress "ingress-test" is invalid: spec.rules[0].http.paths[0].backend: Invalid value: "": resource or service backend is required
I then checked kubernetes documentation here: https://kubernetes.io/docs/concepts/services-networking/ingress/#the-ingress-resource
Based on that, I changed the backend configuration to probably newer syntax:
spec: rules: - host: www.example.com http: paths: - backend: service: name: secondapp port: number: 80 path: / pathType: ImplementationSpecific
With that spec, I succeeded in creating the Ingress Rule ...
BTW, I upgraded to 1.19.6 instead of 1.19.0 in Lab4.1 because I got some message in step 7 there asking me to upgrade to the latest 1.19 version (which was 1.19.6 then)
Thanks and kind Regards,
Wolfgang1 -
During the upgrade you can pick any version in the process, you are not required to upgrade to the latest version.
If the apiVersion is
v1
, then the new syntax needs to be followed, however, I have seen some issues when theIngress
resource would jump back and forth between the two versions. The most stable at the time was also the easiest way, with the least amount of typing, to stay onv1beta1
instead.Regards,
-Chris0
Categories
- 8.9K All Categories
- 13 LFX Mentorship
- 66 LFX Mentorship: Linux Kernel
- 363 Linux Foundation Boot Camps
- 230 Cloud Engineer Boot Camp
- 70 Advanced Cloud Engineer Boot Camp
- 25 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 860 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 102 LFD103 Class Forum
- 3 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 432 LFD259 Class Forum
- 86 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 694 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 26 LFS241 Class Forum
- 28 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 9 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 109 LFS253 Class Forum
- 793 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 51 LFS260 Class Forum
- 79 LFS261 Class Forum
- 14 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 181 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 187 LFW211 Class Forum
- 104 LFW212 Class Forum
- 878 Hardware
- 207 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 724 Linux Distributions
- 82 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 126 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 447 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 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
- 500 Off Topic
- 120 Introductions
- 193 Small Talk
- 19 Study Material
- 748 Programming and Development
- 240 Kernel Development
- 474 Software Development
- 902 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 314 Installation
- 20 All In Program
- 20 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)