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

This way we can ensure cert-manager certs can't be used to create intermediates

Describe the solution you'd like

Add to CertificateSpec struct.

Describe alternatives you've considered

Manually creating a CA cert.

/kind feature

Bug Report

What did you do?
A clear and concise description of the steps you took (or

What would you like to be added:
Ignore IDE files by default in order to not face issues as:

$ kubectl kudo install ./first-operator
Error: failed to resolve package CRDs for operator: ./first-operator: while reading package from the file system: unexpected file when reading package from filesystem: first-operator/.idea/first-operator.iml

The vendors/k8s.io/ directory structure has changed since the guide was written and the Makefile needs to be updated to reflect the change

It would be helpful to have a NatsStreamingCluster example with all possible options just to see everything that is available.

For example in one of the examples it shows setting spec.config.storeDir. what other options are available here other than storeDir?

add documentation to explain how to retrieve ZK_URI based on instance name.
For the first time users, doing a custom installation this can be hard to find

• how to setup the tools stackset-controller + skipper + optional RBAC
• how to use from user point of view (explain traffic) or write a small kubectl plugin stack
• how to create a development environment

I posted kubernetes-sigs/service-apis#173 to generate documentation for service-apis, and I noticed that no documentation is generated for constants of an aliased type.

For example, in the CRD definition, we have:

// GatewayConditionType is a type of condition associated with a Gateway.
type GatewayConditionType string

const (
	// ConditionNoSuchGatewayClass

W0402 16:47:41.924422       1 client_config.go:529] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0402 16:47:41.938128       1 scaling-controller.go:132] SCHEDULED SCALER CREATED: application-hpa-schedule-1 -> application
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code

$ kubectl logs -f storageos-cluster-operator-598bbc4d79-k66qj -n storageos-operator
2019-09-07T02:46:03.279Z INFO storageos.job Creating a new DaemonSet {"Request.Namespace": "default", "Request.Name": "storageos-job"}
2019-09-07T02:46:03.342Z DEBUG kubebuilder.controller Successfully Reconciled {"controller": "job-controller", "request": "default/storageos-job"}
2019-09-07T02:46:03.478Z INFO

When we have more than one ExternalDNS, they appear in the same line which is confusing
We should print each address in its own line.

• goreplay uses elasticsearch storage in non-standard way: you have to setup --http-output to make it work.
• elasticsearch version 6+ is not currently supported. so v5 is a requirement

references:
buger/goreplay#421
elasticsearch-dump/elasticsearch-dump#350