Associated bz https://bugzilla.redhat.com/show_bug.cgi?id=1546156
On Fri, Apr 20, 2018 at 4:45 PM, Seth Jennings wrote:
> Pretty sure this was fixed in this PR that went into 3.9.
> https://github.com/openshift/origin/commit/0727d1d31fad4b4f66eff46fe750f9
> 66fab8c28b
>
>
> On
Pretty sure this was fixed in this PR that went into 3.9.
https://github.com/openshift/origin/commit/0727d1d31fad4b4f66eff46fe750f966fab8c28b
On Fri, Apr 20, 2018 at 12:49 PM, Tim Dudgeon wrote:
> I believe I'm seeing a problem with using GlusterFS volumes when you
> terminate a pod that is usin
That might be the resources you set for the deployed application pod,
but the _builder_ pod, the one with the "-build" suffix, is
BestEffort.
On Mon, Aug 14, 2017 at 10:39 AM, Thorvald Hallvardsson
wrote:
> Hi Derek,
>
> Thank you for your reply.
>
> But as I mentioned in my first post I requeste
Hey Andrew, It is true that we don't generate a pod level event when
a container in the pod is OOM killed. There is a container status in
the pod status that indicates with OOM with status.state.reason set to
OOMKilled.
status:
...
containerStatuses:
- containerID:
docker://f2389dccd11a6575
rrently running on-prem but I'd love to have the ability to
> provision extra capacity on AWS when needed.
>
> Thanks,
> Dave
>
>
> On 30 January 2017 at 15:27, Seth Jennings wrote:
>
>> Upstream kube has this in beta. Origin doesn't support this right n
Upstream kube has this in beta. Origin doesn't support this right now.
The real trick is joining nodes to the cluster. Currently,
openshift-ansible has a playbook for joining nodes to an existing cluster
but that pattern doesn't work really well for node autoscaling.
We are looking at ways to do
(Third time is the charm for Andrew :-/ The mailing list address is messed
up here (us...@redhat.com) and not saying on-list in my previous 2 reply
attempts. Fixing manually.)
This is an issue in upstream Kubernetes for this
https://github.com/kubernetes/kubernetes/issues/26810
It seems that th
I don't think it is a bug in Go. ..data is a symlink, not a directory, os
IsDir() returning false is not unexpected. Unfortunately, there isn't a
way to determine if the symlink points at a file or a directory without
following the link.
However, if you modify your code to skip entries in the di
NFS mounts can be mounted directly into pods without being PVs like this:
volumes:
name: shared
nfs:
server:
path:
If you are using NFS PVs, then the persistentVolumeReclaimPolicy
determines if the data is wiped when the PVC is released. The default
value is "Retain". It will not
Hey Gerard,
I also hit this issue this morning:
https://paste.fedoraproject.org/438222/51651371/
Seems that a recent change to docker (projectatomic/docker) introduced
a regression:
$ git describe
v1.10.3-95-g8b7fa4a
$ git log --oneline a612434.. | grep -i digest
8e24cc3 Merge pull request #194
10 matches
Mail list logo
