Lab 13.1 - Unable to get the short name 'ct' in step 5
As stated in the subject, I'm working through excersice 13.1 and on step 5.
"5. Create the new object and view he resource using short and long name."
I have been successful in previous steps to show both the long and short names. Step 3 worked without issue.
I am receive data back when I use the long name "CronTab".
Please advise,
$ kubectl get crd
NAME AGE
crontabs.training.lfs258.com 25m
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$
$
$ kubectl describe crd
Name: crontabs.training.lfs258.com
Namespace:
Labels: <none>
Annotations: <none>
API Version: apiextensions.k8s.io/v1beta1
Kind: CustomResourceDefinition
Metadata:
Creation Timestamp: 2018-05-26T17:47:43Z
Generation: 1
Resource Version: 1343830
Self Link: /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/crontabs.training.lfs258.com
UID: e470d8c3-610c-11e8-a61b-06901a6654e2
Spec:
Group: training.lfs258.com
Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Scope: Cluster
Version: v1
Status:
Accepted Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Conditions:
Last Transition Time: 2018-05-26T17:47:43Z
Message: no conflicts found
Reason: NoConflicts
Status: True
Type: NamesAccepted
Last Transition Time: 2018-05-26T17:47:43Z
Message: the initial names have been accepted
Reason: InitialNamesAccepted
Status: True
Type: Established
Events: <none>
$ kubectl create -f new-crontab.yaml
Error from server (AlreadyExists): error when creating "new-crontab.yaml": crontabs.training.lfs258.com "new-cron-object" already exists
$
$ kubectl get CronTab
NAME AGE
new-cron-object 22m
$ kubectl describe CronTab
Name: new-cron-object
Namespace:
Labels: <none>
Annotations: <none>
API Version: training.lfs258.com/v1
Kind: CronTab
Metadata:
Cluster Name:
Creation Timestamp: 2018-05-26T17:52:48Z
Resource Version: 1344196
Self Link: /apis/training.lfs258.com/v1/new-cron-object
UID: 9a18bcac-610d-11e8-a61b-06901a6654e2
Spec:
Cron Spec: */5 * * * *
Image: some-cron-image
Events: <none>
$
$
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$
$
$ kubetl get nct
kubetl: command not found
$ kubectl get nct
error: the server doesn't have a resource type "nct"
$ kubectl delete -f new-crontab.yaml
crontab.training.lfs258.com "new-cron-object" deleted
$
$
$ kubectl get CronTab
No resources found.
$ kubectl describe CronTab
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$ kubectl get crd
NAME AGE
crontabs.training.lfs258.com 29m
$ kubectl describe crd
Name: crontabs.training.lfs258.com
Namespace:
Labels: <none>
Annotations: <none>
API Version: apiextensions.k8s.io/v1beta1
Kind: CustomResourceDefinition
Metadata:
Creation Timestamp: 2018-05-26T17:47:43Z
Generation: 1
Resource Version: 1343830
Self Link: /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/crontabs.training.lfs258.com
UID: e470d8c3-610c-11e8-a61b-06901a6654e2
Spec:
Group: training.lfs258.com
Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Scope: Cluster
Version: v1
Status:
Accepted Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Conditions:
Last Transition Time: 2018-05-26T17:47:43Z
Message: no conflicts found
Reason: NoConflicts
Status: True
Type: NamesAccepted
Last Transition Time: 2018-05-26T17:47:43Z
Message: the initial names have been accepted
Reason: InitialNamesAccepted
Status: True
Type: Established
Events: <none>
$
$
$ vim new-crontab.yaml
$
$
$ kubectl create -f new-crontab.yaml
error: unable to recognize "new-crontab.yaml": no matches for kind "CronTab" in version "training.lfs458.com/v1"
$ vim new-crontab.yaml
$
$
$ kubectl create -f new-crontab.yaml
crontab.training.lfs258.com "new-cron-object" created
$
$
$ kubectl get CronTab
NAME AGE
new-cron-object 11s
$
$
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$ kubectl describe ct
error: the server doesn't have a resource type "ct"
Sean
==Output==
$ kubectl get crd
NAME AGE
crontabs.training.lfs258.com 25m
$
$
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$
$
$ kubectl describe crd
Name: crontabs.training.lfs258.com
Namespace:
Labels: <none>
Annotations: <none>
API Version: apiextensions.k8s.io/v1beta1
Kind: CustomResourceDefinition
Metadata:
Creation Timestamp: 2018-05-26T17:47:43Z
Generation: 1
Resource Version: 1343830
Self Link: /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/crontabs.training.lfs258.com
UID: e470d8c3-610c-11e8-a61b-06901a6654e2
Spec:
Group: training.lfs258.com
Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Scope: Cluster
Version: v1
Status:
Accepted Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Conditions:
Last Transition Time: 2018-05-26T17:47:43Z
Message: no conflicts found
Reason: NoConflicts
Status: True
Type: NamesAccepted
Last Transition Time: 2018-05-26T17:47:43Z
Message: the initial names have been accepted
Reason: InitialNamesAccepted
Status: True
Type: Established
Events: <none>
$ kubectl create -f new-crontab.yaml
Error from server (AlreadyExists): error when creating "new-crontab.yaml": crontabs.training.lfs258.com "new-cron-object" already exists
$
$ kubectl get CronTab
NAME AGE
new-cron-object 22m
$ kubectl describe CronTab
Name: new-cron-object
Namespace:
Labels: <none>
Annotations: <none>
API Version: training.lfs258.com/v1
Kind: CronTab
Metadata:
Cluster Name:
Creation Timestamp: 2018-05-26T17:52:48Z
Resource Version: 1344196
Self Link: /apis/training.lfs258.com/v1/new-cron-object
UID: 9a18bcac-610d-11e8-a61b-06901a6654e2
Spec:
Cron Spec: */5 * * * *
Image: some-cron-image
Events: <none>
$
$
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$
$
$ kubetl get nct
kubetl: command not found
$ kubectl get nct
error: the server doesn't have a resource type "nct"
$ kubectl delete -f new-crontab.yaml
crontab.training.lfs258.com "new-cron-object" deleted
$
$
$ kubectl get CronTab
No resources found.
$
$
$
$ kubectl describe CronTab
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$ kubectl get crd
NAME AGE
crontabs.training.lfs258.com 29m
$ kubectl describe crd
Name: crontabs.training.lfs258.com
Namespace:
Labels: <none>
Annotations: <none>
API Version: apiextensions.k8s.io/v1beta1
Kind: CustomResourceDefinition
Metadata:
Creation Timestamp: 2018-05-26T17:47:43Z
Generation: 1
Resource Version: 1343830
Self Link: /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/crontabs.training.lfs258.com
UID: e470d8c3-610c-11e8-a61b-06901a6654e2
Spec:
Group: training.lfs258.com
Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Scope: Cluster
Version: v1
Status:
Accepted Names:
Kind: CronTab
List Kind: CronTabList
Plural: crontabs
Singular: crontab
Conditions:
Last Transition Time: 2018-05-26T17:47:43Z
Message: no conflicts found
Reason: NoConflicts
Status: True
Type: NamesAccepted
Last Transition Time: 2018-05-26T17:47:43Z
Message: the initial names have been accepted
Reason: InitialNamesAccepted
Status: True
Type: Established
Events: <none>
$
$
$ vim new-crontab.yaml
$
$
$ kubectl create -f new-crontab.yaml
error: unable to recognize "new-crontab.yaml": no matches for kind "CronTab" in version "training.lfs458.com/v1"
$ vim new-crontab.yaml
$
$
$ kubectl create -f new-crontab.yaml
crontab.training.lfs258.com "new-cron-object" created
$
$
$ kubectl get CronTab
NAME AGE
new-cron-object 11s
$
$
$ kubectl get ct
error: the server doesn't have a resource type "ct"
$ kubectl describe ct
error: the server doesn't have a resource type "ct"
Comments
-
Hi Sean,
I believe your issue is again yaml whitespace. If all is good in your crd.yaml, describe crd should also show you the Short Names: ct, like below:
... Spec: Group: training.lfs258.com Names: Kind: CronTab List Kind: CronTabList Plural: crontabs Short Names: ct ...
If in your crd.yaml, the "- ct" is not properly alligned, you will not get an error during the create -f crd.yaml, and you will receive the error of unfound resource type. I am not exactly sure why there is no error at create. However, I did notice this before too, and it was also the last line that was giving me headaches.
If all whitespace is correct in crd.yaml, you should be able to obtain successful outputs for all attempts at get ct, get crontab, get crontabs, get CronTab.
If you downloaded the solutions tar file, you should have a good crd.yaml which works.
If not, try this:
apiVersion: apiextensions.k8s.io/v1beta1 kind: CustomResourceDefinition metadata: name: crontabs.training.lfs458.com # This name must match names below. # <plural>.<group> syntax spec: scope: Cluster #Could also be Namespaced group: training.lfs458.com version: v1 names: kind: CronTab #Typically CamelCased for resource manifest plural: crontabs #Shown in URL singular: crontab #Short name for CLI alias shortNames: - ct #CLI short name
Have fun with YAML )
-Chris
0 -
Thanks Chris,
I found a couple of typos in my YAML files that were the cause of my issues with this exercise.
Thank you again for you help.
Sean
0
Categories
- All Categories
- 219 LFX Mentorship
- 219 LFX Mentorship: Linux Kernel
- 793 Linux Foundation IT Professional Programs
- 354 Cloud Engineer IT Professional Program
- 179 Advanced Cloud Engineer IT Professional Program
- 82 DevOps Engineer IT Professional Program
- 147 Cloud Native Developer IT Professional Program
- 137 Express Training Courses
- 137 Express Courses - Discussion Forum
- 6.2K Training Courses
- 47 LFC110 Class Forum - Discontinued
- 71 LFC131 Class Forum
- 42 LFD102 Class Forum
- 226 LFD103 Class Forum
- 19 LFD110 Class Forum
- 38 LFD121 Class Forum
- 18 LFD133 Class Forum
- 7 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 5 LFD210 Class Forum
- 5 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 697 LFD259 Class Forum
- 111 LFD272 Class Forum
- 4 LFD272-JP クラス フォーラム
- 12 LFD273 Class Forum
- 149 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 2 LFS116 Class Forum
- 4 LFS118 Class Forum
- LFS120 Class Forum
- 7 LFS142 Class Forum
- 5 LFS144 Class Forum
- 4 LFS145 Class Forum
- 3 LFS146 Class Forum
- 3 LFS147 Class Forum
- 1 LFS148 Class Forum
- 15 LFS151 Class Forum
- 2 LFS157 Class Forum
- 30 LFS158 Class Forum
- 7 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 32 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム
- 18 LFS203 Class Forum
- 134 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 52 LFS241 Class Forum
- 48 LFS242 Class Forum
- 38 LFS243 Class Forum
- 15 LFS244 Class Forum
- 2 LFS245 Class Forum
- LFS246 Class Forum
- 49 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 153 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 9 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.3K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 119 LFS260 Class Forum
- 159 LFS261 Class Forum
- 42 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 23 LFS268 Class Forum
- 30 LFS269 Class Forum
- LFS270 Class Forum
- 202 LFS272 Class Forum
- 2 LFS272-JP クラス フォーラム
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 9 LFW111 Class Forum
- 259 LFW211 Class Forum
- 181 LFW212 Class Forum
- 13 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 796 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 103 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 758 Linux Distributions
- 82 Debian
- 67 Fedora
- 17 Linux Mint
- 13 Mageia
- 23 openSUSE
- 148 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 353 Ubuntu
- 468 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 63 Mobile Computing
- 18 Android
- 33 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 371 Off Topic
- 114 Introductions
- 174 Small Talk
- 22 Study Material
- 805 Programming and Development
- 303 Kernel Development
- 484 Software Development
- 1.8K Software
- 263 Applications
- 183 Command Line
- 3 Compiling/Installing
- 987 Games
- 317 Installation
- 97 All In Program
- 97 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)