What would you like to be added:

Enable Dynamic Persistent volume Provisioning for ceph rbd provisioner through adding "allowVolumeExpansion" parameter.

Why is this needed:

Dynamic Persistent volume Provisioning is necessary and ceph rbd support this.

In README.md there is the following command:

docker run --it  --name tgr -p 5000:5000 -e CLIENT_ID="xxxxxxx" -e CLIENT_SECRET="xxxxxxxxxxxxxxx" -e DEBUG="True" tgr

There is two issues with that:

1. It should be -it, rather than --it, since the first one is invalid
2. You also need to specify -e HOST="0.0.0.0" and -e PORT="5000" in order for the app to start.

Addi

Before creating a feature request, please search existing feature requests to see if you find a similar one. If there is a similar feature request please up-vote it and/or add your comments to it instead

Why do you want this feature?
When draining nodes on a production cluster, it might be safer to use a health check between node/nodegroup draining loops - to ensure that until now things

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as

Describe the solution you'd like
It would be neat to see the start time of plugins when looking at sonobuoy status. For example, when E2E are running, they may take a while, but when did they start?

$ sonobuoy status                                                                                                            
PLUGIN		STATUS		COUNT
e2e		running		1
systemd_logs	comple

环境：

• Mac
• vagrant 2.1.2
• virtualBox: 5.2.16
• Kubernetes 1.11.0

遇到了几个问题：

1. 在系统自动挂起之后vm 的时间会不对，没有自动同步，导致 Prometheus 监控数据显示不出来，应该同步时间就可以，不过我没有，而是使用的 vagrant halt ，就导致了另一个问题。
2. 执行 vagrant halt 按照【重启】 的操作后，之前配置的 Istio 相关所有东西都不见了，包括 istio-system namespace 。
3. 按照[文档](

Describe the bug/feature
I would like kapitan to output unindented sequences.
At the moment it generates

mylist:
  - item1
  - item2

and I want

mylist:
- item1
- item2

The current behaviour seems deliberate (https://github.com/deepmind/kapitan/blob/25f4ebaca159a748e44683a45875e74be73c1570/kapitan/utils.py#L163-L170 ) but I would like to be able to deactivate

I'm have quite a bit of difficulties trying to get started. First I tried building and running the match docker image with an Elasticsearch connectionstring in the form of https://xxx:xxx@provider:port which does not work. Then I tried to rebuild the docker container using different types of setup based on the Elasticsearch python lib documentation e.g.:

es = Elasticsearch(
    ['local

Contributors are very welcome but while talking with people willing to contribute or contributing already it seems that getting started is difficult.

This task can be a good starting point for a new contributor willing to understand how the project works.

https://goreleaser.com may be better than the crap I threw together.

Is this a BUG REPORT or FEATURE REQUEST?:
This is a BUG REPORT about the documentation or the go script responsible of the scrapping of the kismatic-cluster.yaml file

What happened:

When you define a cluster with internal ip with the following key: internal_ip the ansible generated inventory don't take it as internal.

The result of ansible generated inventory look likes this

In GUIDE.md, in the "Start up the Kubernetes dashboard" section, the kubectl apply ... command is referencing a resource that no longer exists. Here's the kubectl apply ... command from the guide along with the response:

$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/aio/deploy/altern

Repository Description:

This guide should help fellow researchers and hobbyists to easily automate and accelerate there deep leaning training with their own Kubernetes GPU cluster.

should be

accelerate their deep leaning training

There are in other helm chart many nice example documentation in comments of values.yaml, we don't have much of that. See for example GitLabs' Helm charts for GitLab itself or GitLab runners and note how they use ## and # differently. Also read ab

Hi! thanks for open sourcing this big effort!

Would it be possible to compare this solution to Kubeflow which contains Seldon-Core and an example.

And finally, if you have some time, compare to [PipelineAI](https://

Create a new view to provide insights on resource recommendations:

• aggregation key for the resource recommendation
• first timestamp of the histogram
• total number of samples in the histogram
• graphical display of the CPU/memory histogram
• percentiles (e.g. p50, p90, p99) from histograms

what

When using Teleport tsh login to connect to a cluster, although kubectl works fine, kops does not, because, in general, the Teleport name of the cluster is not the same as the kops cluster name. This leads to an error like

 ⧉  staging (staging:default)+
 √ : (cpco-staging-admin) helmfiles ⨠ kops validate cluster
Validating cluster us-west-2.staging.cpco.io

Cannot load k

• Update Architecture Diagram
• rename Openwhisk to cloud functions
• Reorganize readme if needed
• rename Bluemix to IBM Cloud
• Test on new version of spring boot and kubernetes - open pr: #42, #43
• Test the serverless functions - (replicate issue #35) need to update readme
• Spring Boot on Open Liberty

The README mentions how to update Grafana Dashboards and Prometheus Alert Rules.
However it doesnt have infos how to update the stack/services itself.

• Can one simply pull latest code and re-run ./deploy script and expect it to deploy any updated services/configs?
• Do you have to run the ./teardown beforehand and will it persist/reattach the storage and data to the newly created stack

Project readme seems outdated in some parts. Maybe we can update it?
Especially "We plan to release all required components to the community in Q2/2018."