-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[keycloak] Rename environment variables. #13791
[keycloak] Rename environment variables. #13791
Conversation
Can one of the admins verify this patch? |
1 similar comment
Can one of the admins verify this patch? |
@davidfestal any idea about that? |
Yes, in the latest versions of the Keycloak docker image, the environment variable names have changed. |
Can one of the admins verify this PR? |
@davidfestal ok but it doesn't look like che deployment (with helm or deploy_che.sh) are affected by this problem. Is it because these deployments are using an older keycloak image? cc @skabashnyuk |
Just by my rough inspection, the vanilla K8s controller will apply |
@monaka I belive that |
@skabashnyuk I'm not sure how scripts in Looks both Even if the issue above, The pain point I guess is ... After I wrote above. I found the issue what I want to say. helm/charts#9561 |
I updated the patch in this PR as I found the issue #13821. |
ci-test |
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to test that but +1 to merge this PR as soon as @monaka is ready and @eclipse/eclipse-che-qa is ok.
@monaka Pod logs: |
@mkuznyetsov Thank you for your checking and report. It may be required to apply some more patches to Dockerfile for |
POSTGRES_* to DB_*. Signed-off-by: Masaki Muranaka <[email protected]>
Signed-off-by: Masaki Muranaka <[email protected]>
DB_VENDOR is parsed in `docker-entrypoint.sh`. `standalone.sh` will be called the tail of `docker-entrypoint.sh.` Signed-off-by: Masaki Muranaka <[email protected]>
@mkuznyetsov I pushed the additional patch here. (And I pushed the patched docker image into https://hub.docker.com/r/monaka/che-keycloak for saving time and effort.) I checked my deployment by Helm boot up with no error on my AKS cluster. |
ci-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@monaka thank you, it works now.
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
@eclipse/eclipse-che-qa do you see any issues in test results? |
ci-build |
@monaka if you don't mind I want to merge it to make it part of RC4 |
-Dkeycloak.migration.strategy=IGNORE_EXISTING \ | ||
-Dkeycloak.migration.dir=/scripts/ \ | ||
-Djboss.bind.address=0.0.0.0 | ||
exec /opt/jboss/docker-entrypoint.sh -Dkeycloak.migration.action=import \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why the change of script here? what does docker-entrypoint.sh do that standalone.sh doesn't? (Also, aside, "container-entrypoint" would be better. :) )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please read docker-entrypoint.sh that stored in the base image.
Some important environment variables are parsed in there. standalone.sh
is called by docker-entrypoint.sh
after parsing.
It's best to ask maintainers of the jboss-dockerfiles
organization (not me) if you don't like the name docker-entrypoint.sh
.
@skabashnyuk I see. I pressed |
Signed-off-by: Masaki Muranaka [email protected]
I noticed when I deployed
eclipse/che-keycloak:nightly
NOT by using Helm nor Openshift.So this patch is not tested well. But I believe multiuser deployments will be failed without this patch.
I can't determine if this is critical or not. As this is only critical for users who want to the multiuser env.
What does this PR do?
Renames environment variables applying to the
che-keycloak
instance.PORTGRES_PORT_5432_TCP_ADDR to POSTGRES_ADDR .
POSTGRES_PORT_5432_TCP_PORT to POSTGRES_PORT .
What issues does this PR fix or reference?
refs #13625