[OKD 4.x]: first preview drop - please help out with testing and feedback

2019-11-20 Thread Daniel Comnea
Hi folks, For those who are not following the okd working group updates or not hanging on the openshift-dev/users K8s slack channel, please be aware of the announcement sent out [1] by Clayton We would very much appreciate if folks help out testing and provide feedback. Note we haven't

Tencrypt: Hardening OpenShift by Encrypting Tenant Traffic (concept proposal, feedback welcome!)

2018-12-07 Thread Dominik Pataky
from Pods towards Pods of the same OpenShift Project, without the need for any changes in deployment images (hence „transparent“). Feedback very welcome! I would be very happy about input, as my next (current) student thesis will extend Tencrypt. Published blog article: https://dpataky.eu/l

Fwd: [e2e] Simple pre-flight checks for 'oc adm diag', feedback needed

2017-10-30 Thread Bogdan Dobrelya
(Cross posting to the original mail thread) Forwarded Message Subject: [e2e] [aos-devel] Simple pre-flight checks for 'oc adm diag', feedback needed Date: Mon, 30 Oct 2017 09:59:59 +0100 From: Bogdan Dobrelya <bdobr...@redhat.com> Organization: Red Hat To:

[e2e] [aos-devel] Simple pre-flight checks for 'oc adm diag', feedback needed

2017-10-30 Thread Bogdan Dobrelya
Could I please ask for a code review and feedback for a new openshift-ansible pre-flight connectivity check [0]? Note that it implements an empty place-holder for the connectivity check (and tag) to follow the standard interface for auto-detecting and listing all the available checks and tags

Simple pre-flight checks for 'oc adm diag', feedback needed

2017-10-25 Thread Bogdan Dobrelya
Hello folks. Sometimes it makes sense to perform some pre-flight checks for provisioned nodes, like DNS resolve and connectivity check/ping, *before* to deploy a cluster, wait for ~30 min, and then see 'oc adm diagnostics' fails for your cluster because of the hosts' DNS/connectivity issues

Re: feedback

2016-12-06 Thread Jessica Forrester
: *Srinivas Naga Kotaru <skot...@cisco.com>, Jessica Forrester < > jforr...@redhat.com> > *Cc: *dev <dev@lists.openshift.redhat.com> > *Subject: *Re: feedback > > > > > > > On Dec 6, 2016, at 3:13 PM, Srinivas Naga Kotaru (skotaru) < > skot...@cisco

Re: feedback

2016-12-06 Thread Clayton Coleman
On Dec 6, 2016, at 3:13 PM, Srinivas Naga Kotaru (skotaru) < skot...@cisco.com> wrote: we are continuously hearing 2 complaints from our users not much verbose info to troubleshott/narrow down 2 commonf failures . 1. Pod unable to come up. Why it failed, what caused?

feedback

2016-12-06 Thread Srinivas Naga Kotaru (skotaru)
we are continuously hearing 2 complaints from our users not much verbose info to troubleshott/narrow down 2 commonf failures . 1. Pod unable to come up. Why it failed, what caused? 2. Deployment failure. Why it failed ? what is the reason? Most clints using console,

Re: Feedback needed: Automating Kubernetes / OpenShift integrations - i.e. building your own controllers

2016-09-08 Thread Clayton Coleman
Thanks for the feedback - some comments inline > On Sep 8, 2016, at 3:44 AM, Tobias Florek <opensh...@ibotty.net> wrote: > > Hi! > > I did not play with it yet but did find the docs: > https://github.com/openshift/origin/blob/master/docs/man/man1/oc-observe.1 > > I

Re: Feedback needed: Automating Kubernetes / OpenShift integrations - i.e. building your own controllers

2016-09-08 Thread Tobias Florek
Hi! I did not play with it yet but did find the docs: https://github.com/openshift/origin/blob/master/docs/man/man1/oc-observe.1 I wrote a few simple kubernetes/openshift controllers in bash and did not find it too hard. There was quiet a bit of overhead though: watching in one container,