|
43 | 43 | S3Bucket(s) reference S3Connection(s) objects. Both types of objects can be referenced by other resources. For example in a DruidCluster you can specify a bucket for deep storage and an S3Connection for data ingestion.
|
44 | 44 | S3Connection objects can be defined in a standalone fashion or they can be inlined into a bucket object. Similarly a bucket can be defined in a standalone object or inlined into an enclosing object.
|
45 | 45 |
|
46 |
| -[excalidraw,s3-cluster-bucket-connection-reference,svg,width=70%] |
47 |
| ----- |
48 |
| -include::partial$diagrams/S3ResourceOverview.excalidraw[] |
49 |
| ----- |
| 46 | +image::s3-overview.drawio.svg[TODO alt text] |
50 | 47 |
|
51 | 48 | The diagram above shows three examples of how the objects can be
|
52 | 49 | structured.
|
|
78 | 75 |
|
79 | 76 | The inline definition is variant 3 in the figure above.
|
80 | 77 |
|
81 |
| -[excalidraw,s3-cluster-bucket-connection-reference,svg,width=70%] |
82 |
| ----- |
83 |
| -include::partial$diagrams/S3ResourcesInlined.excalidraw[] |
84 |
| ----- |
| 78 | +image::s3-inline.drawio.svg[TODO alt text] |
85 | 79 |
|
86 | 80 | This variant has the advantage that everything is defined in a single file, right where it is going to be used:
|
87 | 81 |
|
@@ -111,10 +105,7 @@ spec:
|
111 | 105 |
|
112 | 106 | Often multiple buckets are used across a data pipeline, as well as buckets being used by different applications, so stand-alone resource definitions that can be referenced from multiple objects make sense.
|
113 | 107 |
|
114 |
| -[excalidraw,s3-cluster-bucket-connection-reference,svg,width=70%] |
115 |
| ----- |
116 |
| -include::partial$diagrams/S3ResourcesByReference.excalidraw[] |
117 |
| ----- |
| 108 | +image::s3-fully-separated.drawio.svg[TODO alt text] |
118 | 109 |
|
119 | 110 | The DruidCluster references the S3Bucket, which in turn references the S3Connection. First the definition of the S3Connection:
|
120 | 111 |
|
|
0 commit comments