Alan McGinlay

When I use `control-tower` to deploy an instance of concourse named, for example, `amcginlay` it conveniently creates a `fly target` named `control-tower-amcginlay`. Once I’ve deployed Concourse I’m no longer concerned...

It seems like we've gone from a solution which supported PAS & PKS tiles side-by-side (pks=true) to one which supports only one or the other. Aside from concerns about what...

Also, in `venafi-issuer.yaml` the attribute `spec.venafi.cloud.url` is no longer required and its inclusion as specified causes a failure. [This](https://cert-manager.io/docs/configuration/venafi/) documentation has it correct.

Also, the certificate manifest needs a `commonName` so, for example: ``` ... spec: secretName: demo-jetstack-mcginlay.net-tls dnsNames: - demo.jetstack.mcginlay.net commonName: demo.jetstack.mcginlay.net ... ```

May I also suggest we rename this tutorial from "Securing Ingresses with Venafi" to "EKS + Ingress + Venafi" so it matches the pattern established by "GKE + Ingress +...

This problem also emerges when one tries to deploy meshed resources via Helm. IMO we have a precedent for how it should work. Compare, for example, what happens when you...

Latest thinking is that this behaviour is better classified as intermittent. Investigations are ongoing by submitter.

FWIW a fix was applied to a **copy** of this source code over at https://github.com/paulternate/cf-venafi-automation/commit/d26da136117c812cec45a5697c57ede329102a22. Anticipating this change can be folded back in here when this issue is addressed.