You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/product-information.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,15 +54,15 @@ Stackable components.
54
54
=== Operators and products
55
55
56
56
All operators are supplied in container images. The products are also deployed in container images. The docker images
57
-
are available for download here: https://repo.stackable.tech/#browse/browse:docker[]
57
+
are available for download here: https://oci.stackable.tech/[]. Information on how to browse the images can be found xref:contributor:project-overview.adoc#docker-images[here].
58
58
59
59
Stackable supports installing the Operators via https://helm.sh/[Helm] or with <<stackablectl>>. Every Operator includes
60
60
installation instructions in the Getting started guide.
61
61
62
62
==== Helm Charts
63
63
64
-
The Helm Charts can be found here: https://repo.stackable.tech/#browse/browse:helm-stable[] Using the Helm Charts
65
-
requires Helm version 3 or above.
64
+
The Helm Charts can be found here: https://oci.stackable.tech/api/v2.0/projects/sdp-charts[] Using the Helm Charts
65
+
requires Helm version 3 or above. Information on how to browse the OCI repository for Helm Charts is described xref:contributor:project-overview.adoc#product-artifacts[here].
Copy file name to clipboardExpand all lines: modules/concepts/pages/product-image-selection.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ At the bottom of this page in the <<_common_scenarios, common scenarios>> sectio
75
75
76
76
== Stackable provided images
77
77
78
-
If your Kubernetes cluster has internet access, the easiest way is to use the publicly available images from the https://docker.stackable.tech/[Image registry hosted by Stackable] (as has been noted at the beginning of the page):
78
+
If your Kubernetes cluster has internet access, the easiest way is to use the publicly available images from the https://oci.stackable.tech/[Image registry hosted by Stackable] (as has been noted at the beginning of the page):
79
79
80
80
[source,yaml]
81
81
----
@@ -99,7 +99,7 @@ Security updates within a release line will result in patch version bumps in the
99
99
If you don't specify the Stackable version, the operator will use its own version, e.g. `23.7.0`.
100
100
When using a nightly operator or a `pr` version, it will use the nightly `0.0.0-dev` image.
101
101
102
-
All the available images (with their product and stackable version) can be found in our https://repo.stackable.tech/#browse/browse:docker:v2%2Fstackable[docker repository].
102
+
All the available images (with their product and stackable version) can be found in our https://oci.stackable.tech/api/v2.0/projects/sdp[OCI registry]. Information on how to browse the registry can be found xref:contributor:project-overview.adoc#docker-images[here]).
103
103
104
104
== Custom docker registry
105
105
@@ -117,7 +117,7 @@ spec:
117
117
repo: my.corp/myteam/stackable
118
118
----
119
119
120
-
This will change the image from the default Stackable repository `docker.stackable.tech/stackable/kafka:3.3.1-stackable23.7.0` to `my.corp/myteam/stackable/kafka:3.3.1-stackable23.7.0`.
120
+
This will change the image from the default Stackable repository `oci.stackable.tech/sdp/kafka:3.3.1-stackable23.7.0` to `my.corp/myteam/stackable/kafka:3.3.1-stackable23.7.0`.
121
121
122
122
== [[customimages]] Custom images
123
123
@@ -140,7 +140,7 @@ Only when the correct product version is given to the operator, the product will
140
140
Using custom images has a few limitations that users should be aware of:
141
141
142
142
* The images will *have* to have the same structures that Stackable operators expect.
143
-
This should usually be ensured by specifying a Stackable image in the `FROM` clause of the Dockerfile (all the available images can be found in our https://repo.stackable.tech/#browse/browse:docker:v2%2Fstackable[docker repository] - the schema is typically: `docker.stackable.tech/stackable/<product>:<product-version>-stackable<stackable-version>`).
143
+
This should usually be ensured by specifying a Stackable image in the `FROM` clause of the Dockerfile (all the available images can be found in our https://oci.stackable.tech/api/v2.0/projects/sdp[OCI registry] - the schema is typically: `oci.stackable.tech/sdp/<product>:<product-version>-stackable<stackable-version>`. Information on how to browse the registry can be found xref:contributor:project-overview.adoc#docker-images[here]).
144
144
145
145
* Images will have to be upgraded for every new Stackable release to follow structural changes that Stackable may have made to their images.
146
146
When deriving images from official Stackable images this will mean updating the version of the image in the `FROM` clause to the correct Stackable release.
Similar to the previous command, the API call uses pagination again. So the `page` value in the command can be incremented to see more results. Here the `page_size`
174
+
parameter was also used to increase the results per page.
175
+
176
+
Another possibility, instead of using `curl`, would be the https://github.com/google/go-containerregistry/blob/main/cmd/crane/README.md[crane tool], which can also be used
177
+
to browse the tags when given the path to a repository.
Copy file name to clipboardExpand all lines: modules/contributor/pages/testing-on-kubernetes.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ The easiest way that we found to do this is by using https://github.com/tilt-dev
87
87
Tilt should then automatically discover this registry from the cluster config and push images there.
88
88
89
89
If you are using a remote cluster, Tilt will push the generated container images to a remote registry, in order for your Kubernetes to be able to access them.
90
-
We have configured `docker.stackable.tech/sandbox` as the default registry, as this is what all our developers use.
90
+
We have configured `oci.stackable.tech/sandbox` as the default registry, as this is what all our developers use.
91
91
External contributors will not have access to this registry and need to override this to a registry of their choice.
92
92
93
93
Overriding the default registry can be done by providing a file called `tilt_options.json` in the same directory as the Tiltfile.
:description: Customize Stackable product images by modifying base images, deploying to a registry or Kubernetes cluster, and configuring your Stacklet to use them.
@@ -21,12 +21,12 @@ To use a customized image you have to:
21
21
22
22
The Stackable operators rely on the structure and contents of the product images, so any modifications need to be done using the Stackable images as base images.
23
23
24
-
You can find the Stackable Docker images in the {stackable-docker-registry}[Stackable Docker registry].
25
-
Images follow a naming schema: `docker.stackable.tech/stackable/<product>:<product-version>-stackable<stackable-version>` where `<product>` are the products like `druid`, `trino` and `opa`, `<product-version>` are product versions like `28.0.1`, `414` or `0.61.0` and `<stackable-version>` is a Stackable platform version like `23.7` or `24.3.0`.
24
+
You can find the Stackable Docker images in the {stackable-oci-registry}[Stackable OCI registry].
25
+
Images follow a naming schema: `oci.stackable.tech/sdp/<product>:<product-version>-stackable<stackable-version>` where `<product>` are the products like `druid`, `trino` and `opa`, `<product-version>` are product versions like `28.0.1`, `414` or `0.61.0` and `<stackable-version>` is a Stackable platform version like `23.7` or `24.3.0`.
26
26
The Stackable version can also be `0.0.0-dev` for nightly images.
27
27
You can use this naming schema together with the xref:operators:supported_versions.adoc[] list to quickly find the base image you need.
28
28
29
-
For example, you might use the `docker.stackable.tech/stackable/hive:3.1.3-stackable24.3.0` image as a base for a modified Apache Hive image where you add a custom database driver.
29
+
For example, you might use the `oci.stackable.tech/sdp/hive:3.1.3-stackable24.3.0` image as a base for a modified Apache Hive image where you add a custom database driver.
30
30
Use the `FROM` clause in your Dockerfile to reference the base image.
31
31
32
32
When tagging the image, there are no requirements by the operator, any registry and tag is possible.
@@ -60,4 +60,5 @@ With this configuration the operator deploys your Stacklet using your custom ima
60
60
== Further reading and useful links
61
61
62
62
* Read about xref:concepts:product-image-selection.adoc[] to learn about other ways of specifying a product version or images, for example how to use a custom registry when mirroring Stackable images.
63
-
* Have a look at the {stackable-docker-registry}[Stackable Docker registry] to find out which images are available to use as a base.
63
+
* Have a look at the {stackable-oci-registry}[Stackable OCI registry] to find out which images are available to use as a base. Information on how to browse the registry
64
+
can be found xref:contributor:project-overview.adoc#docker-images[here].
0 commit comments