Error: 'internal error creating kubernetes cluster' on DSM while provisioning Postgres Database
search cancel

Error: 'internal error creating kubernetes cluster' on DSM while provisioning Postgres Database

book

Article ID: 393322

calendar_today

Updated On: 04-16-2025

Products

VMware Data Services Manager

Issue/Introduction

Symptoms:

While provisioning Postgres database on DSM, it will stay at "InProgress" state.

When click on information button, the below information and error would show up.

[
  {
    "lastTransitionTime": "2025-03-21T06:33:00Z",
    "message": "",
    "observedGeneration": 1,
    "reason": "InProgress",
    "status": "False",
    "type": "Ready"
  },
  {
    "lastTransitionTime": "2025-03-21T06:36:23Z",
    "message": "internal error creating kubernetes cluster: Get \"https://10.##.##.1:6443/api/v1/namespaces?timeout=10s&timeoutSeconds=10\": tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, 10.##.138.7, not 10.##.241.1: error provisioning kubernetes cluster",
    "observedGeneration": 1,
    "reason": "Failed",
    "status": "False",
    "type": "Provisioning"
  },
  {
    "lastTransitionTime": "2025-03-21T06:33:01Z",
    "message": "",
    "observedGeneration": 1,
    "reason": "IPAddressWarning",
    "status": "False",
    "type": "IPAddressWarning"
  }
]

Sample Screen as below.

Environment

VMware DSM 2.2.1

Cause

This is observed when there is an issue with the IPs used for DSM management layer and DSM databases coming from the same IP pool.

Resolution

In order to resolve the issue, Subnet reservation and IP pool should have a different set of IPs as Subnet reservation is meant for DSM internal and IP pool is for Databases.

Refer: Deploying the VMware Data Services Manager plug-in in vSphere Client