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.

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

Hazelcast Kubernetes configuration #8812

Closed
gbbirkisson opened this issue May 7, 2021 · 1 comment
Closed

Hazelcast Kubernetes configuration #8812

gbbirkisson opened this issue May 7, 2021 · 1 comment
Assignees
Projects
Milestone

Comments

@gbbirkisson
Copy link
Contributor

I want to be able to configure HZ K8s plugin further. Now XP does not provide this option.

See this for reference: https://github.com/hazelcast/hazelcast-kubernetes/tree/v1.5.5

What I need to be able to set:

hazelcast:
  network:
    join:
      kubernetes:
        enabled: true
        namespace: MY-KUBERNETES-NAMESPACE
        service-name: MY-SERVICE-NAME
        resolve-not-ready-addresses: true

Nice to have:

hazelcast:
  network:
    join:
      kubernetes:
        service-label-name: ?
        service-label-value: ?
        pod-label-name: ?
        pod-label-value: ?
        use-node-name-as-external-address: true
        kubernetes-api-retries: 5

partition-group:
  enabled: true
  group-type: NODE_AWARE

Hardly useful, pretty much never set manually:

hazelcast:
  network:
    join:
      kubernetes:
        kubernetes-master: ?
        api-token: ?
        ca-certificate: ?
        service-port: ?
@rymsha rymsha self-assigned this May 7, 2021
@rymsha rymsha added this to To do in 7.7.0 via automation May 7, 2021
@rymsha rymsha added this to the 7.7.0 milestone May 7, 2021
@rymsha rymsha moved this from To do to In progress in 7.7.0 May 10, 2021
rymsha added a commit that referenced this issue May 10, 2021
rymsha added a commit that referenced this issue May 10, 2021
rymsha added a commit that referenced this issue May 10, 2021
@rymsha
Copy link
Contributor

rymsha commented May 10, 2021

All from "Need" and "Nice to have" could be done. We won't implement "Hardly useful"

group-type: NODE_AWARE is little bit tricky. It is a general setting, not related to K8S directly, but sure, let's try it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
7.7.0
Done
Development

No branches or pull requests

3 participants