Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix #653 - Incorrect usage of COHERENCE_CACHE_CONFIG in example yaml … #654

Merged
merged 1 commit into from
May 31, 2024
Merged

Fix #653 - Incorrect usage of COHERENCE_CACHE_CONFIG in example yaml … #654

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/025_extend_client/README.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,7 +232,7 @@ include::manifests/minimal-job.yaml[]

To be able to run the client we need to set in three pieces of information.

* The name of the cache configuration file. We set this using the `COHERENCE_CACHE_CONFIG` environment variable, and set the value to `minimal-client-cache-config.xml`, which is the configuration file we're using in this example.
* The name of the cache configuration file. We set this using the `COHERENCE_CACHECONFIG` environment variable, and set the value to `minimal-client-cache-config.xml`, which is the configuration file we're using in this example.
* The client needs to be able to discover the storage Pods to connect to. Just like the server cluster uses well known addresses to discover a cluster, the client can do the same. We set the `COHERENCE_WKA` environment variable to the name of the WKA service created for the server when we deployed it above, in this case it is `storage-wka`.
* Finally, we set the name of the Coherence cluster the client will connect to. When we deployed the server we did not specify a name, so the default cluster name will be the same as the `Coherence` resource name, in this case `storage`. So we set the `COHERENCE_CLUSTER` environment variable to `storage`.

Expand Down
2 changes: 1 addition & 1 deletion examples/025_extend_client/manifests/minimal-job.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ spec:
- name: client
image: simple-extend-client:1.0.0
env:
- name: COHERENCE_CACHE_CONFIG
- name: COHERENCE_CACHECONFIG
value: minimal-client-cache-config.xml
- name: COHERENCE_WKA
value: storage-wka
Expand Down
2 changes: 1 addition & 1 deletion examples/025_extend_client/manifests/minimal-other-namespace-job.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ spec:
- name: client
image: simple-extend-client:1.0.0
env:
- name: COHERENCE_CACHE_CONFIG
- name: COHERENCE_CACHECONFIG
value: minimal-client-cache-config.xml
- name: COHERENCE_WKA
value: storage-wka.default.svc
Expand Down
Loading