Skip to main content
NetApp Knowledge Base

Cannot add an internally accessible k8s cluster in ACC with public FQDN

Views:
106
Visibility:
Public
Votes:
5
Category:
astra
Specialty:
snapx
Last Updated:

Applies to

  • Astra Control Center (ACC) 23.07
  • Kubernetes cluster (e.g. Openshift 4.12)

Issue

When attempting to add an internal k8s cluster by its external name, you get the following errors:
  • in the composite compute module, two events:
    1. "failed to add cluster" with the next message as error
    2. separate event: "type:https://astra.netapp.io/problems/63, title:Kubeconfig not valid, description:The provided credential can't connect to the cluster. Provide an updated credential and retry the request., status:400, schema_validation_failure:, invalid_params:[], invalid_fields:[]"
  • in the trident service module:
    • event: "errors - error handler - Invalid cluster credentials for provided ID." with error: "could not initialize Kubernetes client; couldn't retrieve API server's version: Get \"https://api-int.<CLUSTER-FQDN>:6443/version\": x509: certificate signed by unknown authority"

These errors (especially the X509 error) come even when adding the following line into the kubeconfig under "cluster":

insecure-skip-tls-verify: true

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.