Can you run the same comment with --v=6 to see what URL is getting denied?
Your policy rule limits permissions to the prod namespace. Does the
deployment you are trying to apply specify a different namespace?
On Thursday, May 4, 2017 at 6:13:10 PM UTC-4, Sen Han wrote:
>
> I am using
+Marcin Wielgus
+Maciek Pytel
--
Filip
On Mon, May 1, 2017 at 4:55 PM, wrote:
> I'm running a Kubernetes 1.6.1 cluster on GKE and recently tried to add
> anti affinity to some of our deployments. I'm running a 3 node cluster of a
> piece of software, currently using 3
On Wed, May 3, 2017 at 12:10 PM, 'Ahmet Alp Balkan' via Kubernetes user
discussion and Q wrote:
> I am afraid it still does not make sense to me.
>
> Why is there even a concept of "Pod-level request/limit" if it is not used
> anywhere?
>
It is used by the
https:///apis/extensions/v1beta1/namespaces/prod/deployments
note that deployments is the only one which is not working, secrets, pods
are all works.
On Friday, May 5, 2017 at 2:12:41 AM UTC-4, Jordan Liggitt wrote:
>
> Can you run the same comment with --v=6 to see what URL is getting
Pretty sure the namespace on the deployment yaml is correct because of I
can 'get' and 'deploy' other resource types just fine such as Secrets etc.
On Fri, May 5, 2017 at 2:12 AM, Jordan Liggitt wrote:
> Can you run the same comment with --v=6 to see what URL is getting
As davidopp@ mentioned a pod is the unit of scheduling. So to find a
suitable node for a pod, the scheduler has to identify a node that sum(all
container requests) available.
It is also used by the node to enforce overall resource usage across all
containers. Not all memory is reclaimed when a
Hi,
After doing a make release, I point my path variables to the _output directory
to pick up client/server binaries.
PATH variables:
/home/ramki/go/src/k8s.io/kubernetes/_output/release-stage/client/linux-amd64/kubernetes/client/bin
Dear Kubernetes User,
If you are using Kubernetes version 1.1 or higher, you can stop reading now.
If you are using a version of Kubernetes version 1.0 or lower, this email
applies to you (you can check your version using “kubectl version”).
Google Container Registry has deprecated
Hi,
I am new to Kubernetes networking and have some basic questions.
I am trying to write a multitenant SDN plugin that implements kubernetes
NetworkPolicy API. My goal is enable customers to
1.Allow only users who were given access in a namespace to create policies.
2.Create network polices