* Drop note about (only) AWS MRs supporting v2
A few of the other providers like GCP and Azure now do. The rest will
fast follow.
Also, it's not misleading to say the others don't support v2. That reads
like they're incompatible, which they're not. They're just not
namespaced yet.
Signed-off-by: Nic Cope <nicc@rk0n.org>
* Only use modern namespaced provider-upjet-aws MRs
* Make sure they're using v2.0.0 providers
* Make sure they use m.example.org style API groups
* Make sure they're namespaced
Signed-off-by: Nic Cope <nicc@rk0n.org>
---------
Signed-off-by: Nic Cope <nicc@rk0n.org>
Added introductory sentence before Operations diagram to match the pattern
used for other diagrams. Explains the SSL certificate monitoring scenario
that the diagram illustrates, connecting the use case to the visual representation.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Changed 'SSL Monitor Operation API' to 'SSL Monitor Operation' in the
mermaid diagram to prevent text truncation that was showing as
'SSL Monitor Operation AP' in the rendered output.
Signed-off-by: Nic Cope <nicc@rk0n.org>
Nic Cope