Bug Report

What did you do?

[kni@provisionhost-0-0 kata-operator]$ operator-sdk version
[Deprecation Notice] Operator SDK has a new CLI and project layout that is aligned with Kubebuilder.
See operator-sdk init -h and the following doc on how to scaffold a new project:
https://v0-19-x.sdk.operatorframework.io/docs/golang/quickstart/
To migrate existing projects to the new layou

Feature Request

Is your feature request related to a problem? Please describe:

We can add a new flag such as host-network. If we run install.sh --host-network, install.sh will open hostNetwork for chaos-daemon.

hostNetwork is also defined in [value.yaml](https://githu

The UI uses the python boto3 library, which doesn't respect the AWS_ENDPOINT environment variable ( boto/boto3#1375 ).

Two updates need to be made, at:
https://github.com/zalando/postgres-operator/blob/master/ui/operator_ui/spiloutils.py#L269
https://github.com/zalando/postgres-operator/blob/master/ui/operator_ui/spiloutils.py#L290

client('s3', endpoint_url=e

Is your feature request related to a problem? Please describe.
Investigate github.com/google/go-containerregistry to replace the heroku/docker-registry-client which seems to be unmaintained.

Describe the solution you'd like
Check the go-containerregistry library and see if it fits our needs.

Describe alternatives you've considered
We already use a forked version of the docker-

What would you like to be added:
Currently, kubectl kudo version only prints the current version of the KUDO CLI. It should also print the version of the KUDO controller if the con

Question

Currently, there are too mach structures contain various informer/control/lister, I think we can define a dedicated structure to store all shared informer/control/lister, like SharedResources or ResourcesHub to avoid pass the parameters everywhere.

We are trying to implement ILM with the Elasticsearch index used by jaeger. All tests were successful and it seems to work without any issue. The only problem is that we require a custom template (additional specification of the ILM policy) to be assigned to the bootstrapped index.

Because elasticsearch will handle the rollover we no longer require the rollover job so we set it to false in the

The kamel init Foo.java command generates source code that has an ASF license header.

But since this is for end users and they may use other licenses or none at all, then we should generally not include a header out of the box. This also makes the code smaller and leaner and quicker to overview and understand.

This applies also to the other languages it can generate for like groovy, kotlin

There is no reason stated in the kubernetes event here:

2s          Warning   CRValidationFailure   Jenkins   Base CR validation failed

The logs:

2019-10-22T09:04:47.894Z        WARN    controller-jenkins      base/validate.go:244    Not found volume for 'backup-script' volume mount in container 'backup' {"cr": "infrastructure", "container": "backup"}
2019-10-22T09:04:47.894Z 

Add example manifests for different persistence options (EBS volume / SSD mount / RAM disk)