I have a cluster running on centos 7, using version 1.6.2 installed by kubeadm.
I'm trying to enable cronjob but kube-apiserver won't start when I add the
config flag.
How I've attempted to do this is by editing
/etc/kubernetes/manifests/kube-apiserver.yaml and adding this line to the
command
Would the new SIG cover GKE matters too?
--
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
When you terminate a pod (either directly or indirectly through more
abstract objects like a Deployment), the kubelet sends a TERM signal to
your pod. You can extend your application to catch this signal, trigger the
shutdown procedure (in your case apparently "send the logs to the other
I'm running a python process (django server) in a pod, which writes its
output to stdout, but attempting to view the logs with "kubctl logs"
shows nothing.
I'm similarly unable to view the logs when I run it as a standalone
docker process (i.e., using "docker logs") - unless I run the docker
+1
On 9 August 2017 at 15:16, 'Adam Worrall' via Kubernetes
developer/contributor discussion wrote:
> I am proposing to create SIG-GCP. It would fill a similar role as SIG-AWS
> and SIG-Azure, but for GCP. Here are the details:
>
> Proposed mission statement:
>
I am proposing to create SIG-GCP. It would fill a similar role as SIG-AWS
and SIG-Azure, but for GCP. Here are the details:
Proposed mission statement:
A Special Interest Group for building, deploying, maintaining, supporting,
and using Kubernetes on the Google Cloud Platform.
Secondary
+1 - there's a lot of good topics that are spread out to other sigs today
which could benefit from being collected together in a consistent
discussion thread.
On Wed, Aug 9, 2017 at 6:16 PM, 'Adam Worrall' via Kubernetes
developer/contributor discussion wrote:
>
There's very little information available for us to help. But it really
seems like an issue with your docker container more than Kubernetes.
You can build and run the docker container locally, and once that is
working, schedule it on Kubernetes and see if it works (it probably will
just work).
+1
On Wed, Aug 9, 2017 at 3:45 PM, Christoph Blecker
wrote:
> +1
>
> On 9 August 2017 at 15:16, 'Adam Worrall' via Kubernetes
> developer/contributor discussion wrote:
>
>> I am proposing to create SIG-GCP. It would fill a similar role as
+1
在 2017年8月10日星期四 UTC+8上午6:16:35,Adam Worrall写道:
>
> I am proposing to create SIG-GCP. It would fill a similar role as SIG-AWS
> and SIG-Azure, but for GCP. Here are the details:
>
> Proposed mission statement:
>
> A Special Interest Group for building, deploying, maintaining, supporting,
>
+1.
On Aug 10, 2017 1:47 AM, "'David Oppenheimer' via Kubernetes
developer/contributor discussion" wrote:
> +1
>
>
> On Wed, Aug 9, 2017 at 3:45 PM, Christoph Blecker
> wrote:
>
>> +1
>>
>> On 9 August 2017 at 15:16, 'Adam Worrall' via
On Friday, June 16, 2017 at 11:24:15 AM UTC-5, pa...@qwil.co wrote:
> Yes, this is the right approach -- here's a detailed walk-through:
>
> https://github.com/johnlabarge/gke-nat-example
>
> On Friday, June 16, 2017 at 8:36:13 AM UTC-7, giorgio...@beinnova.it wrote:
> > Hello, I've the same
yes, i build a docker and incloud those modules
--
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
13 matches
Mail list logo