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
- 10.1K All Categories
- 35 LFX Mentorship
- 88 LFX Mentorship: Linux Kernel
- 502 Linux Foundation Boot Camps
- 278 Cloud Engineer Boot Camp
- 103 Advanced Cloud Engineer Boot Camp
- 47 DevOps Engineer Boot Camp
- 41 Cloud Native Developer Boot Camp
- 2 Express Training Courses
- 2 Express Courses - Discussion Forum
- 1.7K Training Courses
- 17 LFC110 Class Forum
- 4 LFC131 Class Forum
- 19 LFD102 Class Forum
- 148 LFD103 Class Forum
- 12 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 566 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 22 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 44 LFS207 Class Forum
- 298 LFS211 Class Forum
- 53 LFS216 Class Forum
- 46 LFS241 Class Forum
- 40 LFS242 Class Forum
- 37 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 993 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 87 LFS260 Class Forum
- 126 LFS261 Class Forum
- 31 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 21 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 212 LFW211 Class Forum
- 153 LFW212 Class Forum
- 899 Hardware
- 217 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 749 Linux Distributions
- 88 Debian
- 64 Fedora
- 14 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 473 Linux System Administration
- 38 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 63 Mobile Computing
- 22 Android
- 27 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 527 Off Topic
- 127 Introductions
- 213 Small Talk
- 19 Study Material
- 794 Programming and Development
- 262 Kernel Development
- 498 Software Development
- 922 Software
- 257 Applications
- 182 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 53 All In Program
- 53 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)