Kubernetes cluster role admin not able to get deployment status











up vote
0
down vote

favorite












I have the following role:



roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: admin



When I do a kubectl proxy --port 8080 and then try doing



http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}



I get a 200 and everything works fine. However when I do:



http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}/status



I get forbidden and a 403 status back .



I also am able to do get, create, list,watch on deployments with my admin role .



Any idea as to why /status would give forbidden when I clearly have all the necessary permission as admin for my namespace.










share|improve this question




























    up vote
    0
    down vote

    favorite












    I have the following role:



    roleRef:
    apiGroup: rbac.authorization.k8s.io
    kind: ClusterRole
    name: admin



    When I do a kubectl proxy --port 8080 and then try doing



    http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}



    I get a 200 and everything works fine. However when I do:



    http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}/status



    I get forbidden and a 403 status back .



    I also am able to do get, create, list,watch on deployments with my admin role .



    Any idea as to why /status would give forbidden when I clearly have all the necessary permission as admin for my namespace.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have the following role:



      roleRef:
      apiGroup: rbac.authorization.k8s.io
      kind: ClusterRole
      name: admin



      When I do a kubectl proxy --port 8080 and then try doing



      http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}



      I get a 200 and everything works fine. However when I do:



      http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}/status



      I get forbidden and a 403 status back .



      I also am able to do get, create, list,watch on deployments with my admin role .



      Any idea as to why /status would give forbidden when I clearly have all the necessary permission as admin for my namespace.










      share|improve this question















      I have the following role:



      roleRef:
      apiGroup: rbac.authorization.k8s.io
      kind: ClusterRole
      name: admin



      When I do a kubectl proxy --port 8080 and then try doing



      http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}



      I get a 200 and everything works fine. However when I do:



      http://127.0.0.1:8080/apis/extensions/v1beta1/namespaces/cdp/deployments/{deploymentname}/status



      I get forbidden and a 403 status back .



      I also am able to do get, create, list,watch on deployments with my admin role .



      Any idea as to why /status would give forbidden when I clearly have all the necessary permission as admin for my namespace.







      authentication kubernetes amazon-eks






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 10 at 3:26









      Imran

      476316




      476316










      asked Nov 10 at 1:07









      Dipayan

      9710




      9710
























          2 Answers
          2






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          the status subresource doesn't give you any more information than simply fetching the deployment



          The admin role permissions do not let you write deployment status. They let you create and delete the deployment objects, controlling the "spec" portion of the object. Status modification permissions are granted to the deployment controller.






          share|improve this answer




























            up vote
            0
            down vote













            You mentioned verbs of the role and you didn't mention resources and apiGroup. Make sure the following are set:



              - apiGroups:
            - apps
            - extensions
            resources:
            - deployments/status





            share|improve this answer





















              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53235153%2fkubernetes-cluster-role-admin-not-able-to-get-deployment-status%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              1
              down vote



              accepted










              the status subresource doesn't give you any more information than simply fetching the deployment



              The admin role permissions do not let you write deployment status. They let you create and delete the deployment objects, controlling the "spec" portion of the object. Status modification permissions are granted to the deployment controller.






              share|improve this answer

























                up vote
                1
                down vote



                accepted










                the status subresource doesn't give you any more information than simply fetching the deployment



                The admin role permissions do not let you write deployment status. They let you create and delete the deployment objects, controlling the "spec" portion of the object. Status modification permissions are granted to the deployment controller.






                share|improve this answer























                  up vote
                  1
                  down vote



                  accepted







                  up vote
                  1
                  down vote



                  accepted






                  the status subresource doesn't give you any more information than simply fetching the deployment



                  The admin role permissions do not let you write deployment status. They let you create and delete the deployment objects, controlling the "spec" portion of the object. Status modification permissions are granted to the deployment controller.






                  share|improve this answer












                  the status subresource doesn't give you any more information than simply fetching the deployment



                  The admin role permissions do not let you write deployment status. They let you create and delete the deployment objects, controlling the "spec" portion of the object. Status modification permissions are granted to the deployment controller.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 10 at 3:32









                  Jordan Liggitt

                  6,7112421




                  6,7112421
























                      up vote
                      0
                      down vote













                      You mentioned verbs of the role and you didn't mention resources and apiGroup. Make sure the following are set:



                        - apiGroups:
                      - apps
                      - extensions
                      resources:
                      - deployments/status





                      share|improve this answer

























                        up vote
                        0
                        down vote













                        You mentioned verbs of the role and you didn't mention resources and apiGroup. Make sure the following are set:



                          - apiGroups:
                        - apps
                        - extensions
                        resources:
                        - deployments/status





                        share|improve this answer























                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          You mentioned verbs of the role and you didn't mention resources and apiGroup. Make sure the following are set:



                            - apiGroups:
                          - apps
                          - extensions
                          resources:
                          - deployments/status





                          share|improve this answer












                          You mentioned verbs of the role and you didn't mention resources and apiGroup. Make sure the following are set:



                            - apiGroups:
                          - apps
                          - extensions
                          resources:
                          - deployments/status






                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 10 at 3:33









                          Abdennour TOUMI

                          32k15137152




                          32k15137152






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Stack Overflow!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53235153%2fkubernetes-cluster-role-admin-not-able-to-get-deployment-status%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Schultheiß

                              Verwaltungsgliederung Dänemarks

                              Liste der Kulturdenkmale in Wilsdruff