Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Blocker
Fix Version/s: None
Affects Version/s: 8.0.0.Beta
Component/s: HelmChart
Labels:
None

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

8.0.0.GA
Workaround:

Workaround Exists
Workaround Description:

Hide

set JDK11 images in vaules.yaml file to JDK17 images

Show
set JDK11 images in vaules.yaml file to JDK17 images
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

When you have a values.yaml file that is like:

    jdk: "17"
    jdk11:
      builderImage: registry.redhat.io/jboss-eap-8-tech-preview/eap8-openjdk11-builder-openshift-rhel8:latest
      runtimeImage: registry.redhat.io/jboss-eap-8-tech-preview/eap8-openjdk11-runtime-openshift-rhel8:latest
    jdk17:
      builderImage: registry.redhat.io/jboss-eap-8-tech-preview/eap8-openjdk17-builder-openshift-rhel8:latest
      runtimeImage: registry.redhat.io/jboss-eap-8-tech-preview/eap8-openjdk17-runtime-openshift-rhel8:latest

and you create a release:

helm install \
    eap helm-charts/charts/eap8 \
    --replace \
    -f values.yaml \
    --dependency-update

The application is built using JDK11 images instead of JDK17 images;

We used https://github.com/jmesnil/eap-charts/ branch eap8-dev

Assignee:: Jeff Mesnil

Reporter:: Tommaso Borgato

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2023/03/02 12:23 PM

Updated:: 2025/10/31 9:28 AM

Resolved:: 2023/03/02 4:29 PM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates

Hide