Re: [kubernetes-users] Proposal for a new SIG: sig-baiducloud

[Mayur Nagekar]

Hi Zhou,

This is great!

How do you guys spin up a k8s cluster on the baidu cloud ? I ask because we
have kops for AWS and other related eco-system/projects for other clouds.

Also, how can an outside collaborator get access to test k8s stuff on baidu
cloud ?

Regards,
Mayur

On Fri, May 25, 2018 at 3:06 PM, Zhou,Ti  wrote:

> Hi everyone,
>
> I would like to propose a new SIG named sig-baiducloud.
>
> Baidu is a gold member of CNCF and we have a large team working on
> Kubernetes and related projects like complex scheduling, heterogeneous
> computing, auto-scaling etc. We build cloud platform to support Baidu
> emerging business including autonomous driving, deep learning, blockchain
> by leveraging Kubernetes.
>
> Mission statement:
>
> - Building, deploying, maintaining, supporting, and using Kubernetes on
> Baidu Cloud Container Engine(CCE) and Baidu Private Cloud(BPC). Both of the
> project are built on Kubernetes and related CNCF project.
> - Designing, discussing, and maintaining the cloud-provider-baidu
> repository under  github kubernetes project.
>
>
>
> SIG-baiducloud has the similar purpose as other cloud provider SIGs such
> as SIG-aws, SIG-azure, SIG-gcp and SIG-ibmcloud, the purpose of the SIG:
>
> - Identify domain knowledge and work that can be contributed back to
> Kubernetes and related CNCF projects.
> - Mentor CCE and BPC developers to contribute to CNCF projects.
> - Provide an open platform for Baidu Kubernetes community to discuss
> Kubernetes related technologies and share knowledge.
> - Focus on Kubernetes and CNCF related projects, the discussion of
> development issue for CCE and BPC will not be included in the SIG.
>
>
> Initial implementation:
>
> - The SIG will have 3 leaders at any given time, I will be the point of
> contact currently.
>
> - The SIG will follow all pre-requisites as specified by the SIG
> Governance.
>
>
>
> Please let me know if you have any questions.
>
>
> Thanks!
> Ti Zhou
> Kubernetes Contributor & Cloud Architect@Baidu
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] How to remove the directory using kubectl exec command

[Mayur Nagekar]

 If the command you want to execute in the pod has any flags in common
(e.g. -i),

  # you must use two dashes (--) to separate your command's flags/arguments.

  # Also note, do not surround your command and its flags/arguments with
quotes

  # unless that is how you would execute it normally (i.e., do ls -t /usr,
not "ls -t /usr").

  kubectl exec 123456-7890 -i -t -- ls -t /usr
Its all in the help :)
Try:
kubectl exec -n monitoring prometheus-core-5948ff9f7d-zpkt6  -- rm -rf
/prometheus/data/snapshots

On Fri, May 25, 2018 at 12:29 PM,  wrote:

> Hi all ,
>
> I am getting trouble to delete the directory in kubectl exec command i
> have tried following command but getting error
>
> kubectl exec -n monitoring prometheus-core-5948ff9f7d-zpkt6  rm -rf
> /prometheus/data/snapshots
>
> Error
>
> Error: unknown shorthand flag: 'r' in -rf
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] GKE Private cluster - accessing master

[Mayur Nagekar]

What does `kubectl get endpoints kubernetes` show in your case ?

-Mayur

On Thu, May 10, 2018 at 2:28 AM, Vinita  wrote:

> Hi Alan,
>
> Thanks for your reply. I tried your workaround but the certificate is not
> valid for master's internal IP address. I get below error -
> Unable to connect to the server: x509: certificate is valid for
> 35.224.109.130, 10.118.16.1, 172.16.0.2, not 172.16.0.3Thanks,
> Vinita
>
> On Wednesday, May 9, 2018 at 12:03:19 PM UTC-7, Alan Grosskurth wrote:
>>
>> Hi Vinita,
>>
>> I believe the problem is that currently "gcloud container clusters
>> get-credentials" always writes the master's external IP address to
>> ~/.kube/config. So kubectl always talks to that external IP address (via
>> the external IP address of the VM it's running on).
>>
>> You should be able to modify ~/.kube/config on your VM to tell kubectl to
>> talk to the master's internal IP address.
>>
>> First, find the endpoint resource containing the master's internal IP
>> address. For example:
>>
>> $ kubectl get endpoints kubernetes
>> NAME ENDPOINTSAGE
>> kubernetes   172.16.0.1:443   1d
>>
>> Then open ~/.kube/config and find the section for your cluster. For
>> example:
>>
>> apiVersion: v1
>> clusters:
>> - cluster:
>> certificate-authority-data: REDACTED
>> server: https://104.198.205.71
>>   name: gke_myproject_us-central1-c_mycluster
>>
>> Replace the external address (https://104.198.205.71) with the internal
>> address (https://172.16.0.1). The kubectl command should now work,
>> provided Master Authorized Networks allows access from the VM's internal IP
>> address. Note that all of these IP addresses will be different depending on
>> your environment.
>>
>> Let me know if this helps. I agree this isn't very straightforward---I'm
>> looking into potential ways this setup could be improved.
>>
>> Thanks,
>>
>> ---Alan
>>
>> On Tue, May 8, 2018 at 12:01 PM Vinita  wrote:
>>
>>> I have created a private cluster and VM in the same network. I added
>>> VM's internal IP in private cluster's master authorized network. From VM,
>>> after obtaining cluster credentials, I am not able to execute kubectl
>>> commands. However,  if I add VM's external IP to master authorized network
>>> I am able to execute kubectl commands. This behavior is not consistent with
>>> the documentation. Not sure if I am missing something here.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Kubernetes user discussion and Q" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to kubernetes-use...@googlegroups.com.
>>> To post to this group, send email to kubernet...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/kubernetes-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Disappearing k8s master

[Mayur Nagekar]

I think you can try this if not already

1. Sign in to the console <https://console.cloud.google.com/>.

2. On the left side of the top bar, select your project from *Project List*.

3. Open the menu [image: Gallery Menu] on the top left, and click on
*Support*.

5. Your current support package will be displayed.

Reference: https://support.google.com/cloud/#topic=6255036=1


On Sun, Apr 22, 2018 at 10:37 PM, Andrew Howden <he...@andrewhowden.com>
wrote:

> So far as I can see, there *is* no support 
>
> On Sun., 22 Apr. 2018, 4:12 pm Mayur Nagekar, <mayur.nage...@gmail.com>
> wrote:
>
>> Oh, if its managed then you got to write to GKE's support. Not much one
>> can do unless we can investigate by ssh-ing into the master.
>>
>> On Sun, Apr 22, 2018 at 12:25 PM, Andrew Howden <he...@andrewhowden.com>
>> wrote:
>>
>>> Holaa
>>>
>>> On Sat., 21 Apr. 2018, 9:50 pm Mayur Nagekar, <mayur.nage...@gmail.com>
>>> wrote:
>>>
>>>> Can you login into the master and run `docker images` and `docker ps
>>>> -a` ? is the control plane intact/sane ?
>>>>
>>>
>>> Can't login to the master; it's managed but Google Kubernetes Engine.
>>> Thus the bug ^^ it does seem 100% dead though
>>>
>>>> --
>>> Andrew Howden
>>> Careful, well crafted web development.
>>> --
>>> W: https://andrewhowden.com/
>>> PGP: https://pgp.andrewhowden.com (79BAC08A6ED1FF1EABE350A7587D3B
>>> 3A961D2D2D)
>>> --
>>>
>> --
>>>
>> You received this message because you are subscribed to the Google Groups
>>> "Kubernetes user discussion and Q" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to kubernetes-users+unsubscr...@googlegroups.com.
>>> To post to this group, send email to kubernetes-users@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/kubernetes-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>> Thanks,
>>
>> Mayur
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Kubernetes user discussion and Q" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/
>> topic/kubernetes-users/5HIwcxqSSvU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> kubernetes-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to kubernetes-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/kubernetes-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Andrew Howden
> Careful, well crafted web development.
> --
> W: https://andrewhowden.com/
> PGP: https://pgp.andrewhowden.com (79BAC08A6ED1FF1EABE350A7587D3B
> 3A961D2D2D)
> --
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Disappearing k8s master

[Mayur Nagekar]

Oh, if its managed then you got to write to GKE's support. Not much one can
do unless we can investigate by ssh-ing into the master.

On Sun, Apr 22, 2018 at 12:25 PM, Andrew Howden <he...@andrewhowden.com>
wrote:

> Holaa
>
> On Sat., 21 Apr. 2018, 9:50 pm Mayur Nagekar, <mayur.nage...@gmail.com>
> wrote:
>
>> Can you login into the master and run `docker images` and `docker ps -a`
>> ? is the control plane intact/sane ?
>>
>
> Can't login to the master; it's managed but Google Kubernetes Engine. Thus
> the bug ^^ it does seem 100% dead though
>
>> --
> Andrew Howden
> Careful, well crafted web development.
> --
> W: https://andrewhowden.com/
> PGP: https://pgp.andrewhowden.com (79BAC08A6ED1FF1EABE350A7587D3B
> 3A961D2D2D)
> --
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Disappearing k8s master

[Mayur Nagekar]

Also, I'd highly recommend open a bug in k8s repo in github. The responses
are much faster there.
If you happen to do that, please let me know or better copy me. I am
@miyurz there.

On Sun, Apr 22, 2018 at 1:20 AM, Mayur Nagekar <mayur.nage...@gmail.com>
wrote:

> Can you login into the master and run `docker images` and `docker ps -a` ?
> is the control plane intact/sane ?
>
> On Sat, Apr 21, 2018 at 2:05 PM, <he...@andrewhowden.com> wrote:
>
>> On Saturday, April 21, 2018 at 10:31:24 AM UTC+2, he...@andrewhowden.com
>> wrote:
>> > I0421 10:27:53.953721 620 round_trippers.go:417] curl -k -v -XGET
>> -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.8.6
>> (linux/amd64) kubernetes/6260bb0" https://104.155.__XXX__.__XXX__/api
>>
>> Obligatorily, I have actually checked that IP is the one I intended to
>> connect to.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Kubernetes user discussion and Q" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to kubernetes-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to kubernetes-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/kubernetes-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Thanks,
>
> Mayur
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Disappearing k8s master

[Mayur Nagekar]

Can you login into the master and run `docker images` and `docker ps -a` ?
is the control plane intact/sane ?

On Sat, Apr 21, 2018 at 2:05 PM,  wrote:

> On Saturday, April 21, 2018 at 10:31:24 AM UTC+2, he...@andrewhowden.com
> wrote:
> > I0421 10:27:53.953721 620 round_trippers.go:417] curl -k -v -XGET
> -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.8.6
> (linux/amd64) kubernetes/6260bb0" https://104.155.__XXX__.__XXX__/api
>
> Obligatorily, I have actually checked that IP is the one I intended to
> connect to.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Disappearing k8s master

[Mayur Nagekar]

Whats the output of kubectl get nodes ?

On Sat, Apr 21, 2018 at 1:53 PM,  wrote:

> Hola All,
>
> I am struggling with a bug currently that I don't reaaaly know how to
> resolve. In essence, my k8s master has disappeared.
>
> Specifically, it's not available:
>
> - Via kubectl
> - In the admin panel
> - To the (single) node within the cluster
>
> All signs point to it being switched off, or separated by a network
> partition. However, I'm not 100% sure how to debug such a case.
>
> Firstly, it's a personal account -- this particular cluster is "fine"
> (read: I feel stupid when people say my website is down but other than
> that), but I also use these in a professional capacity, for larger
> workloads -- that's suuper scary.
>
> Secondly, it's a cluster that only runs preemptable nodes. They're way
> cheaper and I don't care about small downtimes.
>
> From monitoring, it looks like it died on ~ April 13, 6:19 PM (I think
> AEST?). The cluster itself is fairly talkative until 2018-03-13 10:24:27
> where it no longer logs anything further, or logs are dropped. I would
> guess the former -- the incident will happen as the node gets rotated out,
> not when the master dies.
>
> I'm kiiind of at a loss. It's all still remaining there if a helpful
> Google Cloud person visits these forums (I want to understand the root
> cause so it doesn't happen to other, more important accounts) -- but has
> anyone else seen this?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Thanks,

Mayur

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.