Repository navigation
Conversation
|
🤖 Tue Nov 10 14:18:08 - The preview is ready at: |
laubai
left a comment
There was a problem hiding this comment.
Submitting partial review because potential for power loss
| [NOTE] | ||
| ==== | ||
| As of this writing you will need `make` and Go 1.26. | ||
| ==== |
There was a problem hiding this comment.
The note really interrupts this flow - let's just change the step:
To build and run the binary locally, first install Go 1.26 and `make`, then run the following commands:
| . `./pattern.sh make install-airgap` — install while injecting CA trust and | ||
| registry credentials so Argo CD can sync | ||
|
|
||
| == Patternizer Updates |
There was a problem hiding this comment.
Are the ways to run patternizer what is new here? If not, maybe this should be titled something like "Refresh your Patternizer install"?
It might also be worth directing folks to the docs for this bit, but up to you
| :toc: | ||
| :imagesdir: /images | ||
|
|
||
| == Preamble |
There was a problem hiding this comment.
Not sure if this is always intended to be the first heading in a blog post - it does seem to vary a bit, but not much. If you want something different, maybe something like, "Easily create airgap-ready patterns"?
| Identifying every operator, container image, and Helm chart for a pattern is an | ||
| extremely cumbersome chore—especially when remote charts use wildcard versions. | ||
| We wanted to help with that artifact collection without putting more burden on | ||
| the technician gathering the images. |
There was a problem hiding this comment.
We're missing a concrete premise in our preamble. We need an extra sentence after this to say something like, "With that in mind, we updated patternizer so that it does ... so that you can ... more easily."
| date: 2026-10-26 | ||
| title: Disconnected Patterns UX Update | ||
| summary: We've made some improvements to our disconnected pattern UX | ||
| author: jonny rickard |
There was a problem hiding this comment.
I'm not going to tell you that you MUST capitalize your name, but you are a proper noun, so most English language style guides suggest it. :)
| cp src/patternizer ~/.local/bin/patternizer | ||
| ---- | ||
|
|
||
| == Airgap Capability |
There was a problem hiding this comment.
Maybe "Demo:" or "Example:" with a more descriptive title, e.g. "Demo: Create your own airgap-ready multicloud-gitops pattern"
|
|
||
| === What's happening | ||
|
|
||
| `--extra-config` merges additional operators, images, and Helm entries into the |
There was a problem hiding this comment.
Clarity suggestion:
...into the <<imagesetconfig>> generated by the `init` command.
|
|
||
| Patternizer scrapes the repository for operators, container images, and Helm | ||
| charts. When a remote chart uses a wildcard version, the command resolves the | ||
| latest from the chart repository. The pattern is cloned with full history so |
There was a problem hiding this comment.
Clarity suggestion:
s/so/so that
| === Merged imagesetconfig | ||
|
|
||
| After `--extra-config` is applied, the LVMS and Gitea operator catalogs (and | ||
| their images) are merged with the pattern scrape. That is the file you feed to |
There was a problem hiding this comment.
"That is the file you feed to oc-mirror" isn't super clear - it looks like the output mirror-commands.sh already feeds imagesetconfig.yaml (the merged combination of the base config file and the extra config file) into the oc-mirror command, so is it more accurate to say, e.g.
When you supply additional configuration with the `--extra-config` parameter,
patternizer merges your extra configuration with the base configuration.
It saves the combined output in an imagesetconfig.yaml file
and generates the mirror-commands.sh script, which you can then use
as a starting point to mirror required images to your disconnected registry.
In our example, the final imagesetconfig file includes the
LVMS and Gitea operator catalogs and their images
on top of the original multicloud-gitops configuration.
| if you have not already. In this lab the registry is Quay mirror-registry on the | ||
| bastion, and the cluster is brought up with the agent-based installer—see | ||
| <<lab-environment>> and <<agent-install>>. | ||
| ==== |
There was a problem hiding this comment.
Rather than the IMPORTANT admonition, I'd suggest just listing out any steps that are not covered in this blog.
It looks like the mirror-commands.sh sets a few values and then suggests commands to run with appropriate values filled in. Are the following sections just repeating the process it suggests with different commands because of our lab setting, to be clear about what we did in our lab?
No description provided.