Fwd: Take the Kubernetes Application Survey

[Clayton Coleman]

OpenShift users!  Please take a moment to participate in the Kubernetes
application survey - your feedback will help make Kubernetes and OpenShift
a better platform.

Thanks!


Begin forwarded message:

*From:* Matt Farina 
*Date:* April 5, 2018 at 11:40:11 AM EDT
*To:* "Kubernetes developer/contributor discussion" <
kubernetes-...@googlegroups.com>,  kubernetes-sig-apps <
kubernetes-sig-a...@googlegroups.com>,  kubernetes-wg-app-def <
kubernetes-wg-app-...@googlegroups.com>, cncf-kubernetes-h...@lists.cncf.io
*Subject:* *Take the Kubernetes Application Survey*

The survey is available at https://goo.gl/forms/ht61kKETiqVR103v1

Backstory: For the past several months the App Def WG has been looking at
how people build applications to run on Kubernetes and tools to work with
them. In order to better understand end users a survey has been created to
learn from a broader audience. The questions have been gathered from a
variety of sources, including sub-project teams, and the resulting data
will be shared with the community at large.

If you build applications for Kubernetes or operates applications on
Kubernetes we ask that you take a few minutes to let us know what you think.

If you would, please share this survey with your networks so we can get
input from a wide audience range.

Thank you.

-- 
You received this message because you are subscribed to the Google Groups
"Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to kubernetes-dev+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/kubernetes-dev/CAMPAG2oYEfgWxt%3DHd7PQTE7TO%2BkSqWN-xc%2BzEjWxBBrm44drZg%40mail.gmail.com

.
For more options, visit https://groups.google.com/d/optout.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: 3.7 Service Catalog Questions

[Walters, Todd]

Thank you Jeff. I’ve been able to get it to install and include the tsb and 
asb.  I’ve noticed though that I had to run installer (config.yml) to generate 
the cert and key/values for the config-map 
‘extension-apiserver-authentication’
 because just run of service-catalog.yml fails because the 
requestheader-client-ca-file
Is not created.  After running the installer, then the service catlog playbook, 
it succeeds and the api server can start properliy.

Thanks,
Todd

From: Jeff Peeler 
Date: Thursday, April 5, 2018 at 3:03 PM
To: "Walters, Todd" 
Cc: "users@lists.openshift.redhat.com" 
Subject: Re: 3.7 Service Catalog Questions


On Tue, Mar 27, 2018 at 11:54 AM, Walters, Todd 
> wrote:
I have several questions about service catalog that I’m trying to work through. 
 I’ve upgraded from 3.6 to 3.7 using the 3.7 upgrade playbook. This has worked 
well.
I then am able to finally successfully run the service-catalog playbook with 
TSB and ASB.  I have had some issues with the install, primarily the api-server 
pod not starting because of problems with the 
extension-apiserver-authentication configmap and not getting the right ca file.

These installer issues have been fixed and to the best of my knowledge released 
now.

I’ve got this to work now but in my testing I have noticed some changes. For 
example, should the service-catalog deployment use daemonsets or deployment 
configs?  If I create with the playbook, from 3.7 it creates daemonsets for the 
kube-service-catalog project for controller manager and api server. If I 
manually create the namespace and process the service-catalog ‘template’ from 
git hub, it creates deployment configs.  Which is correct? Most docs I see say 
edit the dc when talking about service-catalog.

I assume by processing the template from github, you're referring to this 
template?
https://github.com/openshift/origin/blob/ce742c8267add01a63cbdc6402c9287978ce9024/examples/service-catalog/service-catalog.yaml
The ansible installer is for production deployments, while the above template 
is used for a developer environment. The usage of a DaemonSet for catalog 
running in production is intentional. The main difference between the two is 
that daemon sets ensure pods are running per node (based on label selector) 
versus deploymentconfigs which are concerned with the pod count.
These links should help explain further:
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#what-is-a-daemonset
https://docs.openshift.org/latest/architecture/core_concepts/deployments.html#deployments-and-deployment-configurations
https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/


The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. UNIGROUP.COM


___
users mailing list
users@lists.openshift.redhat.com

Re: 3.7 Service Catalog Questions

[Jeff Peeler]

On Tue, Mar 27, 2018 at 11:54 AM, Walters, Todd 
wrote:

> I have several questions about service catalog that I’m trying to work
> through.  I’ve upgraded from 3.6 to 3.7 using the 3.7 upgrade playbook.
> This has worked well.
> I then am able to finally successfully run the service-catalog playbook
> with TSB and ASB.  I have had some issues with the install, primarily the
> api-server pod not starting because of problems with the
> extension-apiserver-authentication configmap and not getting the right ca
> file.
>

These installer issues have been fixed and to the best of my knowledge
released now.


> I’ve got this to work now but in my testing I have noticed some changes.
> For example, should the service-catalog deployment use daemonsets or
> deployment configs?  If I create with the playbook, from 3.7 it creates
> daemonsets for the kube-service-catalog project for controller manager and
> api server. If I manually create the namespace and process the
> service-catalog ‘template’ from git hub, it creates deployment configs.
> Which is correct? Most docs I see say edit the dc when talking about
> service-catalog.
>

I assume by processing the template from github, you're referring to this
template?
https://github.com/openshift/origin/blob/ce742c8267add01a63cbdc6402c9287978ce9024/examples/service-catalog/service-catalog.yaml

The ansible installer is for production deployments, while the above
template is used for a developer environment. The usage of a DaemonSet for
catalog running in production is intentional. The main difference between
the two is that daemon sets ensure pods are running per node (based on
label selector) versus deploymentconfigs which are concerned with the pod
count.

These links should help explain further:
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#what-is-a-daemonset
https://docs.openshift.org/latest/architecture/core_concepts/deployments.html#deployments-and-deployment-configurations
https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users