-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add keycloak to k8s for ingress nginx #21447
Conversation
generators/kubernetes/templates/registry/jhipster-registry.yml.ejs
Outdated
Show resolved
Hide resolved
Co-authored-by: Matt Raible <[email protected]>
I've been testing this for the last couple of days and can't get it to work on macOS. I was able to get everything to start on my M1, but I had to build M1-compatible images and deploy those to Docker Hub. We should change the commands that are output to the console for deploying directly since they don't currently contain
I've been talking with @indiepopart and ideally, this should work after installing this branch: First, start Minikube and enable ingress:
You will need to use the output of Then, create a microservices stack and run the
|
@indiepopart I think we need to document a couple of things for this PR and Minikube:
The best place to add documentation for Minikube is probably https://www.jhipster.tech/kubernetes/. However, I'm not sure people will see it there, so outputting it to the console might be a good idea too. |
I woud rather change the generator and documentation so it works for also for macOS or Windows. Avoid using the minikube ip and nip.io. |
@mraible The README was updated with instructions to use |
Add Keycloak prod deployment to k8s sub-generator for ingress nginx edge option, including PostgreSQL database and clustering. HTTPS/TLS is not configured. This allows testing on minikube.
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (below reviewers) and adding
skip-ci
label, you can still see CI build result at your branch.