Feedback: db with access controls for the crossplane cluster

Nobody has claimed this yet.

Hi,

as you are asking for feedback, I would like to write down my experience with the Linode provider.

Previously, I used the Crossplane Terraform provider and the Linode provider for Terraform. I wanted to try the Crossplane Linode provider this time.

My goal was relatively simple:

- install crossplane on my LKE cluster
- create a postgres cluster
- allow all the IPs of the LKE cluster to access it
- create databases for my apps

I managed to create the postgres cluster. I needed to look for examples for the providerConfig in the GitHub repo, but overall it went smoothly.

I could not figure out how to get the list of K8s node instance IPs into a list for restricting access to those IPs. At this point I gave up.

I hope, this use case helps you to further improve the provider. I'm looking forward to give it another try in a couple of months.

The issue names no source files, tests, or entry points. Investigate how the provider exposes PostgreSQL access controls and how Kubernetes node IPs could be supplied as an allowlist; done means documenting or implementing a supported way to restrict the database to all LKE node IPs.

Written by the indexing model from the issue text.