Conversation
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…letech/documentation into feature/arm-experimental
adwk67
left a comment
adwk67
left a comment
There was a problem hiding this comment.
Sorry for all the comments/suggestions!
Accepting comments of Andrew, thank you! Co-authored-by: Andrew Kenworthy <andrew.kenworthy@stackable.de>
fhennig
left a comment
fhennig
left a comment
There was a problem hiding this comment.
I'd suggest to rename the file to "arm64-support.adoc" (so no experimental) but add the experimental to the title (i.e. "Multi-architecture for SDP (experimental").
Otherwise if we stabilize this feature, the link will change, and that will be annoying.
|
|
||
| By declaring `--set image.repository=docker.stackable.tech/stackable-experimental/commons-operator` you will overwrite the image selected by default with one located in the organization `stackable-experimental`. The other operators can be installed in the same way. | ||
|
|
||
| WARNING: You have to install every operator you need for a given demo individually with helm using `--skip-release` with stackablectl. Otherwise, it will try to install x86 operators and pull ARM64 product images afterwards. |
There was a problem hiding this comment.
I'm not sure what this sentence means? The docs so far only mention helm and helm is used to install the operators? This is confusing.
There was a problem hiding this comment.
Yes, we have to install operators using helm and using stackablectl --skip-release to install a demo. This is because stackablectl operator install kafka=23.11.0 would point to docker.stackable.tech/stackable/kafka-operator:23.11.0 .
I see that this is bad timing to hint it and I overlooked helm *and* using. Would this make it more clear?
I want to inform about --skip-release as it would only be mentioned in the command on the bottom.
|
|
||
| SDP release 23.11.0 has been ported to the ARM64 architecture. These images are stored within the `stackable-experimental` organization in our https://repo.stackable.tech/#browse/browse:docker:v2%2Fstackable-experimental[Nexus]. | ||
|
|
||
| As they are not available by default so you need to first switch to the `stackable-experimental` organization before pulling them for use with the data platform. |
There was a problem hiding this comment.
Not available to whom? By what? How do I switch?
There was a problem hiding this comment.
Through our default access ways. Default refers to docker.stackable.tech/stackable/....
I understand you need to somehow know what I mean. Is this more clear? :
switch from docker.stackable.tech/stackable to docker.stackable.tech/stackable-experimental before pulling images from the repository.
|
Can you please add a link to the generated documentation? |
5 participants
First draft of an small article about early access to our arm64 images