Skip to content

Conversation

@MattDodsonEnglish
Copy link
Collaborator

No description provided.

@tomhollingworth tomhollingworth marked this pull request as ready for review January 6, 2026 14:25
MattDodsonEnglish and others added 16 commits January 7, 2026 07:51
* [Feat] document v4 cluster size (#198)

* [Feat] document v4 cluster size

* Apply fixes from review

* feat: update connector guide to include new options and fix some formatting issues

* Apply suggestions from code review

* fix: move seeq guide from user guides to deploy and from v4.0.0 version to latest

---------

Co-authored-by: Matt Dodson <47385188+MattDodsonEnglish@users.noreply.github.com>
…oak containers (docker.io/keycloak/keycloak:v26)

Update Keycloak events export commands to use kcadm.sh config credentials and proper export syntax for both Kubernetes and Docker deployments. This improves clarity and security by avoiding password input in commands.
Updated documentation to replace NATS with Kafka as a supported protocol for publish-subscribe workflows across multiple guides.
@CFitzgerald212
Copy link

CFitzgerald212 commented Jan 19, 2026

@tomhollingworth
Regarding the backup page, I think we should make a note that the user needs to port forward alpha or shell into alpha for step 4 in the backups.

Additionally, on v4-dev, using the admin account to get an access token, I'm running into the following error in the backup query: "errors":[{"message":" unauthorized type Manifest"}],"data":null

Finally, the backup mutation seemed to work, however approximately an hour later, there is nothing in the configured storage bucket. I can see the mutation said the backup is scheduled, could you please provide some insight into that and maybe describe it further in the documentation?

@tomhollingworth
Copy link
Contributor

tomhollingworth commented Jan 21, 2026

Regarding the backup page, I think we should make a note that the user needs to port forward alpha or shell into alpha for step 4 in the backups.

@CFitzgerald212 please update and make commits against this PR

Finally, the backup mutation seemed to work, however approximately an hour later, there is nothing in the configured storage bucket. I can see the mutation said the backup is scheduled, could you please provide some insight into that and maybe describe it further in the documentation?

I have no insight without diverting and digging into it, I think I've used S3 only once or twice locally. Do you have capacity for this? I won't get to it in a timely manner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants