Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
This is a parent Jira to group all the issues that need to be fixed to improve Ozone's ability to run as a service within Kubernetes.
Attachments
Issue Links
- is a parent of
-
HDDS-1506 Ozone Manager can't be started with existing reverse dns
- Open
-
HDDS-1933 Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change
- Open
-
HDDS-4745 Cannot change Ratis port in existing cluster
- Open
-
HDDS-5114 Do not store datanode details in SCM pipeline db
- Open
-
HDDS-5916 DNs in pipeline raft group get stuck in infinite leader election in Kubernets env
- Resolved
-
HDDS-5919 In kubernettes om HA has circular dependency on the service availability
- Resolved
-
HDDS-6442 SCM HA on Kubernetes failed
- Resolved
-
HDDS-1480 Ip address should not be a part of the DatanodeID since it can change
- Open
-
HDDS-5471 Enable SCM HA in ozone-ha Kubernetes example
- Resolved
- is related to
-
HDDS-6677 Not able to access the Ozone cluster running in Kuberenets through hdfs dfs -put/cat via hadoop client from external network
- Open
-
HDDS-5528 Fix kubernetes tests to work with the latest version of k3s tool
- Open
-
HDDS-4893 Issues with running on kubernetes cluster
- Open
- relates to
-
HDDS-5388 CSI mount failed with kubernetes
- Resolved
-
HDDS-6345 OM always runs OOM in Kubernetes
- Resolved