Welcome to the new Linux Foundation Forum!

Typos

tommcf64tommcf64 Posts: 1
edited January 2017 in LFS258 Class Forum

Typos

Slide 2.11 Kubernetes Users

Kubernetes is being adopted at a very rapid page.

Should be?

Kubernetes is being adopted at a very rapid pace.

Lab Three  Page 3

$ docker run exec -ti k8s etcdctl ls /registry

Should be?

$ docker exec -ti k8s etcdctl ls /registry

..

Comments

  • sporteboissportebois Posts: 10
    edited January 2017

    In slide 6.6, 


    kubectl get deployments, pods

     

    Should be 


    kubectl get deployments,pods

     

    The extra space before pods will otherwise return an error rather than the getting the 2 resource types: 


    error: arguments in resource/name form must have a single resource and name
  • sebgoasebgoa Posts: 23
    edited January 2017

    Thanks for the catch, you are correct. We will update the pages as fast as possible.

    -sebastien

     

  • fcioancafcioanca Posts: 214
    edited March 2017

    Thank you for letting us know. The corrections in the course will be made available once we release an updated version of the course.

    Regards,

    Flavia

  • MinuxMinux Posts: 7

    This yml file refer to a namespace 258 instead of 248 ;-)

    cat redis-lfs248.yaml                                                                                                                                                         

    apiVersion: v1

    kind: Pod

    metadata:

      namespace: lfs258

      name: redis

    spec:

      containers:

        - name: redis

          image: redis

  • MinuxMinux Posts: 7

    In the last block of the slide:


    api/extensions/v1beta1

    should be 


    apis/extensions/v1beta1

     

  • "docker run exec -ti k8s etcdctl ls /registry" should be "docker exec -ti k8s etcdctl ls /registry" <-- Came here to say this. I got very frustrated trying to figure out why the command wasn't working. Took a break for a few days, came back with fresh eyes, and spotted "run" as the problem. 

    Thanks all for updating with other command errors/typos/errata. Next time I will check here first instead of banging my head against the wall.

  • MinuxMinux Posts: 7

    docker run exec -ti k8s etcdctl ls /registry

    should be


    docker exec -ti k8s etcdctl ls /registry

     

  • MinuxMinux Posts: 7
    edited March 2017

    kubectl run ghost —image=ghost

    should be


    kubectl run ghost --image=ghost

     

  • MinuxMinux Posts: 7
    edited March 2017

    Root cause should be when you made the pdf conversion ?

    kubectl expose deployment/ghost --port=2368 —type=NodePort 

    instead of:

    kubectl expose deployment/ghost --port=2368 --type=NodePort 

  • auaaua Posts: 3
    edited March 2017

    For the line "(for a refresher on how to access the Course Resources, look at page 1.9)",

    it should be "page 1.8" not "page 1.9"

  • auaaua Posts: 3
    edited March 2017

    For the line "(for a refresher on how to access the Course Resources, look at page 1.9)",

    it should be "page 1.8" not "page 1.9"

  • auaaua Posts: 3

    $ kubectl exec -ti redis-5o0i8 bash [email protected]:/data# redis-cli 127.0.0.1:6379&gt;

    should be 


    $ kubectl exec -ti redis-5o0i8 bash [email protected]:/data# redis-cli 127.0.0.1:6379&gt;

     

  • simple HHTP servers

  • edited May 2017

    outdated command ?

    $ kubectl get rc --all-namespaces | grep dns

    -no results

    on kubernetes 1.5 and later I think is replica sets instead of replication controllers.

    $ kubectl get rs --all-namespaces | grep dns

    kube-system   kube-dns-2431531914                  1         1         1         1h

  • kevinfparkerkevinfparker Posts: 1
    edited May 2017

    On slide 3.6.a the word "loose" is uwsed rather the intended word "lose"

    Thanks for the course!

     

  • sebgoasebgoa Posts: 23
    edited June 2017

    thank you all , all typos should have been corrected in the latest version of the course.

  • ChristyMasonChristyMason Posts: 1
    edited June 2017

    "Loose" has not been corrected yet.

  • fcioancafcioanca Posts: 214
    edited June 2017

    Thank you, Christy, for letting us now. We will correct it in a future course update.

     

  • hhoerlhhoerl Posts: 1
    edited November 2017

    The default config is in ${HOME}/.kube/config (or ~/.kube/config or something like that ...) and not in $/.kube/config.

  • BearSuBearSu Posts: 1
    edited December 2017

    1. 


    brew install kuberbetes-helm

    shoud be


    brew install kubernetes-helm

     

    2. 

    I use OSX and have installed Homebrew. But when I run the command:


    brew init

    It shows:


    Error: Unknown command: init

    Maybe the command can be ignored, and just run the command:


    helm init

     

  • sjentzschsjentzsch Posts: 1
    edited May 1

    There is an effort to use Google's protobug serialization, but this remains experimental.

    Not sure if intended, but might be a typo xD

  • serewiczserewicz Posts: 416

    Yes, a typo. It should be protobuf  - as in protocol buffer. 

    Thanks!

  • simonh88simonh88 Posts: 1
    edited May 25

    On the $curl line there is a missing o in authorization in header.

    The endpoint doesn't seem to need the auth though as it works fine misspelled or ommited.

     

  • fcioancafcioanca Posts: 214
    edited May 25
    Thank you for pointing this out. It will be corrected in the next course update.
  • sdalzielsdalziel Posts: 16
    edited May 26

    Second sentance of the second paragraph"

    "..., you will receive and error,"

    -corrected to-

    "..., you will receive an error."

  • serewiczserewicz Posts: 416

    Not one but at least two people went through things lookiing for typos and issues. Thank you all very much for letting us know what you have found. Early next week I will be using each of your notes to update the material.

    Your efforts are very much appreciated!

    Kind regards,

     

  • sdalzielsdalziel Posts: 16
    edited May 30

    "Kubernetes clusters have to types of users service accounts and normal users,"

    Should be

    "Kubernetes clusters have 2 types of users 'service' accounts and 'normal users'."

     

  • fcioancafcioanca Posts: 214
    edited May 30
    Thank you. We will make corrections in the next course update.
Sign In or Register to comment.