Cluster configuration ConfigMap

Configuration information about your IBM® Cloud Private cluster.

The ConfigMap of ibmcloud-cluster-info in the namespace of kube-public is designed to publish cluster metadata. The ibmcloud-cluster-info ConfigMap in the kube-public namespace publishes IBM Cloud Private cluster metadata. Following is the ConfigMap structure:

kind: ConfigMap
apiVersion: v1
metadata:
  name: ibmcloud-cluster-info
  namespace: kube-public
data:
  edition: "{{ edition }}"
  cluster_name: "{{ clustername }}"
  cluster_ca_domain: "{{ cluster_CA_domain }}"
  cluster_address: "{{ cluster_external_address }}"
  cluster_router_http_port: "{{ router_http_port }}"
  cluster_router_https_port: "{{ router_https_port }}"
  cluster_kube_apiserver_port: "{{ kube_apiserver_secure_port }}"
  proxy_address: "{{ proxy_external_address }}"
  proxy_ingress_http_port: "{{ ingress_http_port }}"
  proxy_ingress_https_port: "{{ ingress_https_port }}"

Following table describes the parameters:

Table 1. ibmcloud-cluster-info ConfigMap parameters
Parameter	Value	Description	Parameter use
edition	edition	IBM Cloud Private image	Shows the IBM® Cloud Private version.
cluster_name	cluster_name	See `cluster_name`.	The name of the cluster.
cluster_ca_domain	cluster_CA_domain	See `cluster_CA_domain`.	External access to the management ingress.
cluster_address	cluster_external_address	See `cluster_lb_address`.	External IP address for the management services in your cluster.
cluster_router_http_port	router_http_port	See `router_http_port`.	HTTP port that is used by the IBM Cloud Private management ingress.
cluster_router_https_port	router_https_port	See `router_https_port`.	HTTPS port that is used by the IBM Cloud Private management ingress.
cluster_kube_apiserver_port	kube_apiserver_secure_port	See `kube_apiserver_secure_port`.	Sets the Kubernetes apiserver secure port.
proxy_address	proxy_external_address	See proxy node, proxy_vip, or proxy_lb_address in `Customizing the cluster with the config.yaml file` and `Setting the node roles in the hosts file`.	The address that the ingress controller uses.
proxy_ingress_http_port	ingress_http_port	See `ingress_http_port`.	HTTP port that is used by the NGINX ingress controller.
proxy_ingress_https_port	ingress_https_port	See `ingress_https_port`.	HTTPS port that is used by the NGINX ingress controller.

You can use the ConfigMap to get cluster information. Consider the following example:

cluster_address: 9.21.58.100
cluster_ca_domain: mycluster.icp
cluster_kube_apiserver_port: "8001"
cluster_router_http_port: "8080"
cluster_router_https_port: "8443"
edition: Enterprise Edition
proxy_address: 9.21.58.101
proxy_ingress_http_port: "80"
proxy_ingress_https_port: "443"

You can get the ConfigMap information by running the following command:

kubectl -n kube-public get configmap ibmcloud-cluster-info -o yaml