running windows Container in Kubernetes over AWS cloud












14















I installed my existing Kubernetes Cluster (1.8) running in AWS using KOPS.



I would like to add Windows Container to the existing cluster but I can not find the right solution! :(



I thought of following these given steps given in:



https://kubernetes.io/docs/getting-started-guides/windows/



I downloaded the node binaries and copied it to my Windows machine (Kubelet, Kube-dns, kube-proxy, kubectl) but I got a little confused about the multiple networking options.



They have also given the kubeadmin option to join the node to my Master, which I have no idea why since I used Kops to create my cluster.



Can someone advise or help me on how I can get my windows node added?










share|improve this question




















  • 1





    First, are you missing the Prerequisites? as per the doc, kube version should be 1.9

    – titogeo
    Sep 25 '18 at 9:32











  • Have you had any success with this?

    – lanoxx
    Nov 12 '18 at 8:10
















14















I installed my existing Kubernetes Cluster (1.8) running in AWS using KOPS.



I would like to add Windows Container to the existing cluster but I can not find the right solution! :(



I thought of following these given steps given in:



https://kubernetes.io/docs/getting-started-guides/windows/



I downloaded the node binaries and copied it to my Windows machine (Kubelet, Kube-dns, kube-proxy, kubectl) but I got a little confused about the multiple networking options.



They have also given the kubeadmin option to join the node to my Master, which I have no idea why since I used Kops to create my cluster.



Can someone advise or help me on how I can get my windows node added?










share|improve this question




















  • 1





    First, are you missing the Prerequisites? as per the doc, kube version should be 1.9

    – titogeo
    Sep 25 '18 at 9:32











  • Have you had any success with this?

    – lanoxx
    Nov 12 '18 at 8:10














14












14








14


4






I installed my existing Kubernetes Cluster (1.8) running in AWS using KOPS.



I would like to add Windows Container to the existing cluster but I can not find the right solution! :(



I thought of following these given steps given in:



https://kubernetes.io/docs/getting-started-guides/windows/



I downloaded the node binaries and copied it to my Windows machine (Kubelet, Kube-dns, kube-proxy, kubectl) but I got a little confused about the multiple networking options.



They have also given the kubeadmin option to join the node to my Master, which I have no idea why since I used Kops to create my cluster.



Can someone advise or help me on how I can get my windows node added?










share|improve this question
















I installed my existing Kubernetes Cluster (1.8) running in AWS using KOPS.



I would like to add Windows Container to the existing cluster but I can not find the right solution! :(



I thought of following these given steps given in:



https://kubernetes.io/docs/getting-started-guides/windows/



I downloaded the node binaries and copied it to my Windows machine (Kubelet, Kube-dns, kube-proxy, kubectl) but I got a little confused about the multiple networking options.



They have also given the kubeadmin option to join the node to my Master, which I have no idea why since I used Kops to create my cluster.



Can someone advise or help me on how I can get my windows node added?







amazon-web-services docker kubernetes windows-container






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 22 at 1:42









Nashical

231




231










asked May 16 '18 at 11:14









user1852104user1852104

894




894








  • 1





    First, are you missing the Prerequisites? as per the doc, kube version should be 1.9

    – titogeo
    Sep 25 '18 at 9:32











  • Have you had any success with this?

    – lanoxx
    Nov 12 '18 at 8:10














  • 1





    First, are you missing the Prerequisites? as per the doc, kube version should be 1.9

    – titogeo
    Sep 25 '18 at 9:32











  • Have you had any success with this?

    – lanoxx
    Nov 12 '18 at 8:10








1




1





First, are you missing the Prerequisites? as per the doc, kube version should be 1.9

– titogeo
Sep 25 '18 at 9:32





First, are you missing the Prerequisites? as per the doc, kube version should be 1.9

– titogeo
Sep 25 '18 at 9:32













Have you had any success with this?

– lanoxx
Nov 12 '18 at 8:10





Have you had any success with this?

– lanoxx
Nov 12 '18 at 8:10












1 Answer
1






active

oldest

votes


















1














KOPS is really good if the default architecture satisfies your requirements, if you need to make some changes it will give you some trouble. For example I needed to add a GPU Node, I was able to add it, but unable to make this process automatic, being unable to create an auto scaling group.



Kops has a lot of pros, like creating all the cluster in a transparent way.



Do you really need a windows node?



If yes, try to launch a cluster using kube-adm, then joining the windows node to this cluster.



Kops will take some time to add this windows nodes feature.






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',
    autoActivateHeartbeat: false,
    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%2f50369413%2frunning-windows-container-in-kubernetes-over-aws-cloud%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    KOPS is really good if the default architecture satisfies your requirements, if you need to make some changes it will give you some trouble. For example I needed to add a GPU Node, I was able to add it, but unable to make this process automatic, being unable to create an auto scaling group.



    Kops has a lot of pros, like creating all the cluster in a transparent way.



    Do you really need a windows node?



    If yes, try to launch a cluster using kube-adm, then joining the windows node to this cluster.



    Kops will take some time to add this windows nodes feature.






    share|improve this answer




























      1














      KOPS is really good if the default architecture satisfies your requirements, if you need to make some changes it will give you some trouble. For example I needed to add a GPU Node, I was able to add it, but unable to make this process automatic, being unable to create an auto scaling group.



      Kops has a lot of pros, like creating all the cluster in a transparent way.



      Do you really need a windows node?



      If yes, try to launch a cluster using kube-adm, then joining the windows node to this cluster.



      Kops will take some time to add this windows nodes feature.






      share|improve this answer


























        1












        1








        1







        KOPS is really good if the default architecture satisfies your requirements, if you need to make some changes it will give you some trouble. For example I needed to add a GPU Node, I was able to add it, but unable to make this process automatic, being unable to create an auto scaling group.



        Kops has a lot of pros, like creating all the cluster in a transparent way.



        Do you really need a windows node?



        If yes, try to launch a cluster using kube-adm, then joining the windows node to this cluster.



        Kops will take some time to add this windows nodes feature.






        share|improve this answer













        KOPS is really good if the default architecture satisfies your requirements, if you need to make some changes it will give you some trouble. For example I needed to add a GPU Node, I was able to add it, but unable to make this process automatic, being unable to create an auto scaling group.



        Kops has a lot of pros, like creating all the cluster in a transparent way.



        Do you really need a windows node?



        If yes, try to launch a cluster using kube-adm, then joining the windows node to this cluster.



        Kops will take some time to add this windows nodes feature.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 21 at 20:06









        Leandro Donizetti SoaresLeandro Donizetti Soares

        37616




        37616
































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f50369413%2frunning-windows-container-in-kubernetes-over-aws-cloud%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

            MongoDB - Not Authorized To Execute Command

            Npm cannot find a required file even through it is in the searched directory

            in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith