istio: mismatch of hostnames when deploying sidecar
Is this the right place to submit this?
- This is not a security vulnerability or a crashing bug
- This is not a question about how to use Istio
Bug Description
Description
I’m currently testing Istio with 1 of my application. This application is a clustered DB who is doing TCP (through port 7999) called between each node for heath check and hostname check.
When I deploy a sidecar from the application I’m getting the following:
2024-03-20 22:11:11.144 Error: UpdatePluginCacheTask::run: XDMP-WRONGHOST: Host 5726652083699477130(ml-cluster-0.ml-cluster.ml.svc.cluster.local) thinks it is really host 4934967208587200779(ml-cluster-1.ml-cluster.ml.svc.cluster.local).
Step to reproduce the issue:
Deploy the Helm chart: https://github.com/marklogic/marklogic-kubernetes/releases/tag/marklogic-1.1.0
Use the following content for the values.yaml :
## Number of Marklogic nodes
replicaCount: 3
## update strategy for MarkLogic and Helm chart upgrades
## It is recommended to use OnDelete updateStrategy as MarkLogic bootstrap host (pod-0) needs to be upgraded first in the cluster
## and OnDelete allows more control over the upgrade and recovery in case of failure.
updateStrategy:
type: OnDelete
## Termination Grace Period
terminationGracePeriod: 120
## Kubernetes cluster domain name
clusterDomain: cluster.local
## Group related settings
group:
## the group name of the current Marklogic Helm Deployment
name: Default
## xdqp encryption for intra cluster network traffic
enableXdqpSsl: false
Activate sidecar injection on the namespace Restart the PODs to have the sidecar injected. Check the Logs file /var/opt/MarkLogic/Logs/ErrorLog.txt
Thanks in advance for your help
Version
I'm using Istiod helm chart.
Istio version : 1.20.3
% kubectl version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.6-eks-508b6b3
% helm version
version.BuildInfo{Version:"v3.13.3", GitCommit:"c8b948945e52abba22ff885446a1486cb5fd3474", GitTreeState:"clean", GoVersion:"go1.20.11"}
Additional Information
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (5 by maintainers)
Hi @bleggett,
It seems that the quick fix did the job. Many thanks for that.
It would be interesting to understand the root cause behind that. If I can be of any help let me know.