Bobcares

All About ConfigMap in GKE

by | Jul 9, 2023

Learn more about configMap in GKE from our experts. Our Google Cloud Support team is here to help you with your questions and concerns.

All About configMap in GKE

In GKE (Google Kubernetes Engine), a ConfigMap is a Kubernetes resource. It helps store configuration data that can be consumed by containers running in a cluster.

All About configMap in GKE

Furthermore, it offers a way to decouple configuration from the container images. This offers more flexibility and easier management of configuration settings.

Today, we are going to take a look at how to define a ConfigMap:

  1. First, we have to specify key-value pairs in a YAML or JSON file.

    For instance, we have to create a file named configmap.yaml with this content:

    apiVersion: v1 kind: ConfigMap metadata: name: my-configmap data: KEY1: value1 KEY2: value2

    Here, the ConfigMap named my-configmap has two key-value pairs: KEY1 with the value value1 and KEY2 with the value value2. Additionally, we can add more key-value pairs as and when needed.

  2. Next, it is time to apply the ConfigMap to our GKE cluster as seen here:

    kubectl apply -f configmap.yaml

    The above command creates the ConfigMap in our GKE cluster.

  3. Then, we can use the ConfigMap in a Pod, by mounting it as environment variables or as a volume.
  4. Now it is time to modify the Pod’s YAML file to include the env section with the environment variables referencing the ConfigMap keys.

    apiVersion: v1 kind: Pod metadata: name: my-pod spec: containers: - name: my-container image: my-image env: - name: ENV_VAR1 valueFrom: configMapKeyRef: name: my-configmap key: KEY1 - name: ENV_VAR2 valueFrom: configMapKeyRef: name: my-configmap key: KEY2

    This will mount the values of KEY1 and KEY2 from the my-configmap ConfigMap as environment variables in the Pod.

  5. We can also modify the Pod’s YAML file to include a volumes section and a volume mount inside the containers section as seen here:

    apiVersion: v1 kind: Pod metadata: name: my-pod spec: containers: - name: my-container image: my-image volumeMounts: - name: config-volume mountPath: /etc/config volumes: - name: config-volume configMap: name: my-configmap

    This will mount the ConfigMap my-configmap as a volume at the path /etc/config inside the Pod.

  6. Then, we can apply the modified Pod YAML file as seen here:

    kubectl apply -f pod.yaml

The above steps will create a COnfigMap in GKE and used it in a Pod.

Let us know in the comments if you need further help.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Techs introduced us to about configMap in GKE.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF